Category | Status | Test name | Information send feedback |
---|---|---|---|
Parent | ![]() |
Domain NS records | Nameserver records returned by the parent servers are: ns2.afternic.com. ['173.201.67.64'] (NO GLUE) [TTL=3600] verification-eefkqe5ysssig5p3tbttqs.ns101.verify.hn. [] (NO GLUE) [TTL=3600] ns1.afternic.com. ['97.74.99.64'] (NO GLUE) [TTL=3600] f.nic.store was kind enough to give us that information.
|
![]() |
TLD Parent Check | Good. f.nic.store, the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check. | |
![]() |
Your nameservers are listed | Good. The parent server f.nic.store has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers. | |
![]() |
DNS Parent sent Glue | The parent nameserver f.nic.store is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. This happens a lot if you have nameservers on different TLD (domain.com for example with nameserver ns.domain.org.) | |
![]() |
Nameservers A records | ERROR: Some of your DNS servers do not have A records at all. I could not find any A records for the following DNS servers: verification-eefkqe5ysssig5p3tbttqs.ns101.verify.hn You must have A records for all of your nameservers. |
|
NS | ![]() |
NS records from your nameservers | NS records got from your nameservers listed at the parent NS are: ns1.namefind.com ['97.74.99.64'] [TTL=3600] ns2.namefind.com ['173.201.67.64'] [TTL=3600] |
![]() |
Recursive Queries | I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. Problem record(s) are:
verification-eefkqe5ysssig5p3tbttqs.ns101.verify.hn 97.74.99.64 173.201.67.64 |
|
![]() |
Same Glue | The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below! | |
![]() |
Glue for NS records | INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are:
verification-eefkqe5ysssig5p3tbttqs.ns101.verify.hn 97.74.99.64 173.201.67.64 You can fix this for example by adding A records to your nameservers for the zones listed above. |
|
![]() |
Mismatched NS records | OK. The NS records at all your nameservers are identical. | |
![]() |
DNS servers responded | Good. All nameservers listed at the parent server responded. | |
![]() |
Name of nameservers are valid | OK. All of the NS records that your nameservers report seem valid. | |
![]() |
Multiple Nameservers | Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me. | |
![]() |
Nameservers are lame | OK. All the nameservers listed at the parent servers answer authoritatively for your domain. | |
![]() |
Missing nameservers reported by parent | FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems!
ns2.namefind.com ns1.namefind.com |
|
![]() |
Missing nameservers reported by your nameservers | ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns2.afternic.com verification-eefkqe5ysssig5p3tbttqs.ns101.verify.hn ns1.afternic.com This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example). |
|
![]() |
Domain CNAMEs | OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. | |
![]() |
NSs CNAME check | OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. | |
![]() |
Different subnets | OK. Looks like you have nameservers on different subnets! | |
![]() |
IPs of nameservers are public | Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like | |
![]() |
DNS servers allow TCP connection | OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default. | |
![]() |
Different autonomous systems | OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down. | |
![]() |
Stealth NS records sent | Stealth NS records were sent:
ns2.namefind.com ns1.namefind.com |
|
SOA | ![]() |
SOA record | The SOA record is: Primary nameserver: ns1.namefind.com Hostmaster E-mail address: dns.jomax.net Serial #: 2023031500 Refresh: 28800 Retry: 7200 Expire: 604800 1 weeks Default TTL: 300 |
![]() |
NSs have same SOA serial | OK. All your nameservers agree that your SOA serial number is 2023031500. | |
![]() |
SOA MNAME entry | WARNING: SOA MNAME (ns1.namefind.com) is not listed as a primary nameserver at your parent nameserver! | |
![]() |
SOA Serial | Your SOA serial number is: 2023031500. This appears to be in the recommended format of YYYYMMDDnn. | |
![]() |
SOA REFRESH | OK. Your SOA REFRESH interval is: 28800. That is OK | |
![]() |
SOA RETRY | Your SOA RETRY value is: 7200. Looks ok | |
![]() |
SOA EXPIRE | Your SOA EXPIRE number is: 604800.Looks ok | |
![]() |
SOA MINIMUM TTL | Your SOA MINIMUM TTL is: 300. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommends a value of 1-3 hours. Your value of 300 is OK. | |
MX | ![]() |
MX Records | Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers! |
WWW | ![]() |
WWW A Record |
Your www.mygifts.store A record is: www.mygifts.store [76.223.54.146] [13.248.169.48] |
![]() |
IPs are public | OK. All of your WWW IPs appear to be public IPs. | |
![]() |
WWW CNAME | OK. No CNAME |
Processed in 0.304 seconds.