| Category | Status | Test Name | Information |
|---|---|---|---|
| Parent | PASS | Missing Direct Parent check | OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion. |
| INFO | NS records at parent servers | Your NS records at the parent servers are: auth00.ns.uu.net. [198.6.1.65 (NO GLUE)] [US] [These were obtained from d0.org.afilias-nst.org]dcens01.un.org. [157.150.192.40] [TTL=86400] [US] secens01.un.org. [157.150.192.2] [TTL=86400] [US] | |
| PASS | Parent nameservers have your nameservers listed | OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there. | |
| WARN | Glue at parent nameservers | WARNING. The parent servers (I checked with d0.org.afilias-nst.org.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain. | |
| PASS | DNS servers have A records | OK. All your DNS servers either have A records at the zone parent servers, or do not need them (if the DNS servers are on other TLDs). A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers. Note that there will be problems if your DNS servers do not have these same A records. |
| NS | INFO | NS records at your nameservers | Your NS records at your nameservers are: auth00.ns.uu.net.
dcens01.un.org. [157.150.192.40] [TTL=86400] secens01.un.org. [157.150.192.2] [TTL=86400] |
| PASS | Open DNS servers | OK. Your DNS servers do not announce that they are open DNS servers. Although there is a slight chance that they really are open DNS servers, this is very unlikely. Open DNS servers increase the chances that of cache poisoning, can degrade performance of your DNS, and can cause your DNS servers to be used in an attack (so it is good that your DNS servers do not appear to be open DNS servers). | |
| PASS | Mismatched glue | OK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers. | |
| FAIL | No NS A records at nameservers | WARNING: Your nameservers do not include any corresponding A records when asked for your NS records. They probably are not returning the A records when asked, which can prevent some other DNS servers from contacting your DNS servers. They should do this if they are authoritative for those A records (in BIND, you should not use 'minimal-responses yes;'). The problem record(s) are: Nameserver 198.6.1.65 did not provide IPs for all NS records. | |
| PASS | All nameservers report identical NS records | OK. The NS records at all your nameservers are identical. | |
| PASS | All nameservers respond | OK. All of your nameservers listed at the parent nameservers responded. | |
| PASS | Nameserver name validity | OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names). | |
| PASS | Number of nameservers | OK. You have 3 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7. | |
| PASS | Lame nameservers | OK. All the nameservers listed at the parent servers answer authoritatively for your domain. | |
| PASS | Missing (stealth) nameservers | OK. All 3 of your nameservers (as reported by your nameservers) are also listed at the parent servers. | |
| PASS | Missing nameservers 2 | OK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers. | |
| PASS | No CNAMEs for domain | OK. There are no CNAMEs for un.org. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. | |
| PASS | No NSs with CNAMEs | OK. There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. | |
| WARN | Nameservers on separate class C's | WARNING: We cannot test to see if your nameservers are all on the same Class C (technically, /24) range, because the root servers are not sending glue. We plan to add such a test later, but today you will have to manually check to make sure that they are on separate Class C ranges. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location. | |
| PASS | All NS IPs public | OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays. | |
| PASS | TCP Allowed | OK. All your DNS servers allow TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems. | |
| INFO | Nameservers versions | Your nameservers have the following versions: 198.6.1.65: No version info available (refused). 157.150.192.40: "Not Telling" 157.150.192.2: "Not Telling" | |
| PASS | Stealth NS record leakage | Your DNS servers do not leak any stealth NS records (if any) in non-NS requests. |
| SOA | INFO | SOA record | Your SOA record [TTL=86400] is: Primary nameserver: secens01.un.org.
Hostmaster E-mail address: root.un.org. Serial #: 2009111801 Refresh: 10800 Retry: 3600 Expire: 604800 Default TTL: 86400 |
| PASS | NS agreement on SOA Serial # | OK. All your nameservers agree that your SOA serial number is 2009111801. That means that all your nameservers are using the same data (unless you have different sets of data with the same serial number, which would be very bad)! Note that the DNSreport only checks the NS records listed at the parent servers (not any stealth servers). | |
| PASS | SOA MNAME Check | OK. Your SOA (Start of Authority) record states that your master (primary) name server is: secens01.un.org.. That server is listed at the parent servers, which is correct.
| |
| PASS | SOA RNAME Check | OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: root@un.org. (techie note: we have changed the initial '.' to an '@' for display purposes). | |
| PASS | SOA Serial Number | OK. Your SOA serial number is: 2009111801. This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. So this indicates that your DNS was last updated on 18 Nov 2009 (and was revision #1). This number must be incremented every time you make a DNS change. | |
| PASS | SOA REFRESH value | OK. Your SOA REFRESH interval is : 10800 seconds. This seems normal (about 3600-7200 seconds is good if not using DNS NOTIFY; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours)). This value determines how often secondary/slave nameservers check with the master for updates. | |
| PASS | SOA RETRY value | OK. Your SOA RETRY interval is : 3600 seconds. This seems normal (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed. | |
| PASS | SOA EXPIRE value | OK. Your SOA EXPIRE time: 604800 seconds. This seems normal (about 1209600 to 2419200 seconds (2-4 weeks) is good). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver. | |
| PASS | SOA MINIMUM TTL value | OK. Your SOA MINIMUM TTL is: 86400 seconds. This seems normal (about 3,600 to 86400 seconds or 1-24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching. |
| MX | INFO | MX Record | Your 2 MX records are: 10 mx15.un.org. [TTL=86400] IP=157.150.184.110 [TTL=86400] [US] 10 mx20.un.org. [TTL=86400] IP=157.150.184.115 [TTL=86400] [US] |
| PASS | Low port test | OK. Our local DNS server that uses a low port number can get your MX record. Some DNS servers are behind firewalls that block low port numbers. This does not guarantee that your DNS server does not block low ports (this specific lookup must be cached), but is a good indication that it does not. | |
| PASS | Invalid characters | OK. All of your MX records appear to use valid hostnames, without any invalid characters. | |
| PASS | All MX IPs public | OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail. | |
| PASS | MX records are not CNAMEs | OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it. | |
| PASS | MX A lookups have no CNAMEs | OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3). | |
| PASS | MX is host name, not IP | OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records). | |
| PASS | Multiple MX records | OK. You have multiple MX records. This means that if one is down or unreachable, the other(s) will be able to accept mail for you. | |
| PASS | Differing MX-A records | OK. I did not detect differing IPs for your MX records (this would happen if your DNS servers return different IPs than the DNS servers that are authoritative for the hostname in your MX records). | |
| PASS | Duplicate MX records | OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources. | |
| PASS | Reverse DNS entries for MX records | OK. The IPs of all of your mail server(s) have reverse DNS (PTR) entries. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. Note that this information is cached, so if you changed it recently, it will not be reflected here (see the 'Reverse DNS Tool' for the current data). The reverse DNS entries are:
110.184.150.157.in-addr.arpa mx15.un.org. [TTL=86400]
115.184.150.157.in-addr.arpa mx20.un.org. [TTL=86400] |
| PASS | Connect to mail servers | OK: I was able to connect to all of your mailservers. | |
| WARN | Mail server host name in greeting | WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record. mx15.un.org claims to be invalid hostname 'UN':
<br /> 220 UN SMTP Server Ready
<br />mx20.un.org claims to be invalid hostname 'UN':
<br /> 220 UN SMTP Server Ready
<br /> | |
| PASS | Acceptance of NULL <> sender | OK: All of your mailservers accept mail from "<>". You are required (RFC1123 5.2.9) to receive this type of mail (which includes reject/bounce messages and return receipts). | |
| PASS | Acceptance of postmaster address | OK: All of your mailservers accept mail to postmaster@un.org (as required by RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1). | |
| PASS | Acceptance of abuse address | OK: All of your mailservers accept mail to abuse@un.org. | |
| INFO | Acceptance of domain literals | WARNING: One or more of your mailservers does not accept mail in the domain literal format (user@[0.0.0.0]). Mailservers are technically required RFC1123 5.2.17 to accept mail to domain literals for any of its IP addresses. Not accepting domain literals can make it more difficult to test your mailserver, and can prevent you from receiving E-mail from people reporting problems with your mailserver. However, it is unlikely that any problems will occur if the domain literals are not accepted (mailservers at many common large domains have this problem). mx15.un.org's postmaster@[157.150.184.110] response:<br />
>>> RCPT TO:<postmaster@[157.150.184.110]><br />
<<< 550 Mailbox unavailable or access denied -- 0
<br />
mx20.un.org's postmaster@[157.150.184.115] response:<br />
>>> RCPT TO:<postmaster@[157.150.184.115]><br />
<<< 550 Mailbox unavailable or access denied -- 0
<br />
| |
| PASS | Open relay test | OK: All of your mailservers appear to be closed to relaying. This is not a thorough check, you can get a thorough one here. mx15.un.org OK: 550 Mailbox unavailable or access denied -Cannot relay. Mailbox not available: not.abuse.see.www.dnsreport.com.from.ip.38.107.191.114@dnsreport.com
<br />mx20.un.org OK: 550 Mailbox unavailable or access denied -Cannot relay. Mailbox not available: not.abuse.see.www.dnsreport.com.from.ip.38.107.191.114@dnsreport.com
<br /> | |
| PASS | SPF record | You have an SPF record. This is very good, as it will help prevent spammers from abusing your domain. Your SPF record (I don't check to see if it is well designed!) is: "v=spf1 ip4:157.150.0.0/16 a:mx3901.un.org a:mx3902.un.org -all" [TTL=86400] |
| WWW | INFO | WWW Record | Your www.un.org A record is: www.un.org. A 157.150.195.10 [TTL=86400] [US] |
| PASS | All WWW IPs public | OK. All of your WWW IPs appear to be public IPs. If there were any private IPs, they would not be reachable, causing problems reaching your web site. | |
| PASS | CNAME Lookup | OK. Some domains have a CNAME record for their WWW server that requires an extra DNS lookup, which slightly delays the initial access to the website and use extra bandwidth. There are no CNAMEs for www.un.org, which is good. | |
| INFO | Domain A Lookup | Your un.org A record is: un.org. A 157.150.195.10 [TTL=86400] |
|
Legend:
|