Work in progress!

Follow IntoDNS on Twitter


Category Status Test name Information
Parent Info Domain NS records Nameserver records returned by the parent servers are:

us2.mercury.orderbox-dns.com.   ['162.251.82.123', '162.251.82.251', '162.251.82.122', '162.251.82.250'] (NO GLUE)   [TTL=3600]
us2.earth.orderbox-dns.com.   ['162.251.82.246', '162.251.82.119', '162.251.82.118', '162.251.82.247'] (NO GLUE)   [TTL=3600]
us2.mars.orderbox-dns.com.   ['162.251.82.124', '162.251.82.252', '162.251.82.125', '162.251.82.253'] (NO GLUE)   [TTL=3600]
us2.venus.orderbox-dns.com.   ['162.251.82.249', '162.251.82.248', '162.251.82.121', '162.251.82.120'] (NO GLUE)   [TTL=3600]

d0.org.afilias-nst.org was kind enough to give us that information.

Pass TLD Parent Check Good. d0.org.afilias-nst.org, 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.
Pass Your nameservers are listed Good. The parent server d0.org.afilias-nst.org 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.
Info DNS Parent sent Glue The parent nameserver d0.org.afilias-nst.org 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.)
Pass Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found.
NS Info NS records from your nameserversNS records got from your nameservers listed at the parent NS are:
Oups! I could not get any nameservers from your nameservers (the ones listed at the parent server). Please verify that they are not lame nameservers and are configured properly.

Pass Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Pass Same Glue Hmm,I do not consider this to be an error yet, since I did not detect any nameservers at your nameservers.
Pass Glue for NS records OK. Your nameservers (the ones reported by the parent server) have no ideea who your nameservers are so this will be a pass since you already have a lot of errors!
Error Mismatched NS records WARNING: One or more of your nameservers did not return any of your NS records.
Pass DNS servers responded Good. All nameservers listed at the parent server responded.
Pass Name of nameservers are valid OK. The nameservers reported by the parent send out nothing as shown above. I can't check nothing so it's a green!
Error Multiple Nameservers ERROR: Looks like you have less than 2 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.
Pass Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
Pass Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers.
Error Missing nameservers reported by your nameservers You should already know that your NS records at your nameservers are missing, so here it is again:

us2.mercury.orderbox-dns.com.
us2.earth.orderbox-dns.com.
us2.mars.orderbox-dns.com.
us2.venus.orderbox-dns.com.

Pass 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.
Pass 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.
Pass Different subnets OK. Looks like you have nameservers on different subnets!
Pass 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
Pass 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.
Pass 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.
Pass Stealth NS records sent Ok. No stealth ns records are sent
SOA Info SOA recordThe SOA record is:
Primary nameserver: 208.91.197.91
Hostmaster E-mail address: hostmaster.thechapmanedge.org
Serial #: 1748553038
Refresh: 10800
Retry: 3600
Expire: 604800   1 weeks
Default TTL: 3600
Pass NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 1748553038.
Warn SOA MNAME entry WARNING: SOA MNAME (208.91.197.91) is not listed as a primary nameserver at your parent nameserver!
Warn SOA Serial Your SOA serial number is: 1748553038. This can be ok if you know what you are doing.
Pass SOA REFRESH OK. Your SOA REFRESH interval is: 10800. That is OK
Pass SOA RETRY Your SOA RETRY value is: 3600. Looks ok
Pass SOA EXPIRE Your SOA EXPIRE number is: 604800.Looks ok
Pass SOA MINIMUM TTL Your SOA MINIMUM TTL is: 3600. 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 3600 is OK.
MX Error MX RecordsOh 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 Info WWW A Record Your www.thechapmanedge.org A record is:
www.thechapmanedge.org  [75.2.103.23] 
Pass IPs are public OK. All of your WWW IPs appear to be public IPs.
Pass WWW CNAME OK. No CNAME

Processed in 0.281 seconds.