DNS Report
View a complete report on the DNS settings for your domain. This tool is designed to assist webmasters and system administrators diagnose DNS related issues. A number of tests are run on your DNS settings with results displayed in an easy to understand manner.
Sign in to enable copy
Sign in to enable export
DNS Report for 'virped.org'
Parent Nameserver Tests
| Status | Test Case | Information |
|---|---|---|
| NS records listed at parent servers | Nameserver records returned by the parent servers are: ken.ns.cloudflare.com. [NO GLUE] [TTL=3600] dee.ns.cloudflare.com. [NO GLUE] [TTL=3600] This information was kindly provided by a0.org.afilias-nst.info. | |
| Domain listed at parent servers | Good! The parent servers have information on your domain. Some other domains (like .co.us) do not have a DNS zone at the parent servers. | |
| NS records listed at parent servers | Good! The parent servers have your NS records listed. If they didn't, people wouldn't be able to find your domain! | |
| Parent servers return glue | OK. The TLD of your domain (org) differs from that of your nameservers (com). As such, the parent servers are not required to send glue. | |
| A record for each NS at parent | OK. The parent servers don't need to have A records for your nameservers since the TLD of your domain (org) differs from that of your nameservers (com). |
Local Nameserver Tests
| Status | Test Case | Information |
|---|---|---|
| NS records at your local servers | NS records retrieved from your local nameservers were: dee.ns.cloudflare.com. [NO GLUE] [TTL=86400] ken.ns.cloudflare.com. [NO GLUE] [TTL=86400] | |
| Glue at local nameservers | Oops! Your local nameservers don't return IP addresses (glue) along with your NS records! This isn't a fatal error but means an extra lookup needs to be performed increasing the load time to your site. You can fix this by adding A records for each of the nameservers listed above. | |
| Same glue at local and parent servers | OK. Since the GTLD for your domain (org) differs from that of your nameservers (com), the result of this test is irrelevant since the parent servers aren't even required to hold the A records for your nameservers. | |
| Same NS records at each local nameserver | Good! All your local nameservers have identical NS records for your domain. | |
| Check that all nameservers respond | Good! All of your nameservers listed at the parent servers responded. | |
| Check all nameservers are valid | Good! All of your nameservers appear to be valid (e.g. are not IP addresses or partial domain names). | |
| Number of nameservers | Good! You have at least 2 nameservers. Whilst RFC218 section 2.5 specifies a minimum of 3, as long as you have 2 or more, you should be ok! | |
| Local nameservers answer authoritatively | Good! All your nameservers answer authoritatively for your domain. | |
| Missing NS records at parent servers | Good! The parent servers have all the nameservers listed for your domain as your local nameservers! | |
| Missing NS records at local servers | Good! Your local servers have all the nameservers listed for your domain that are listed at the parent servers! | |
| No CNAME records for domain | Good! No CNAME records are present for 'virped.org'. RFC1912 section 2.4 and RFC2181 section 10.3 state that there should be no CNAME records if any other records are present for a given domain. | |
| No CNAME records for nameservers | Good! No CNAME records are present for your nameservers. RFC1912 section 2.4 and RFC2181 section 10.3 state that there should be no CNAME records if any other records (e.g. an A record) are present for a nameserver. | |
| Nameservers are on different IP subnets | Good! All your nameservers are in separate class C (/24) subnets. | |
| Nameservers have public IP's | Good! All your NS records have public IP addresses. | |
| Nameservers allow TCP connections | Good! We can establish a TCP connection with each of your nameservers on port 53. Whilst UDP is most commonly used for the DNS protocol, TCP connections are occasionally used. |
Start of Authority (SOA) Tests
| Status | Test Case | Information |
|---|---|---|
| SOA Record | Your Start of Authority (SOA) record is: Primary nameserver: dee.ns.cloudflare.com. Hostmaster E-mail address: dns.cloudflare.com. Serial number: 2381163164 Refresh: 10000 Retry: 2400 Expire: 604800 Minimum TTL: 1800 | |
| All nameservers have same SOA serial number | Good! All your nameservers agree that your SOA serial number is 2381163164 | |
| SOA primary nameserver listed at parent | Good! The primary nameserver listed in your SOA record (dee.ns.cloudflare.com.) is listed at the parent servers! | |
| SOA serial number format | Oops! Your SOA serial number (2381163164) doesn't seem to be in the recommended format (YYYYMMDDnn - where nn is the revision number). This is still OK, however, as long as you are keeping track of your SOA version details. | |
| SOA Refresh value | Good! Your SOA Refresh value (10000) is within the recommended range of 1 hour (3600) to 1 day (86400). | |
| SOA Retry value | Good! Your SOA Retry value (2400) is within the recommended range of 5 minutes (300) to 4 hours (14400). | |
| SOA Expire value | Good! Your SOA Expire value (604800) is within the recommended range of 1 week (604800) to 4 weeks (2419200). | |
| SOA Minimum TTL value | Good! Your SOA Minimum TTL value (1800) is within the recommended range of less than 3 days (259200). |
Mail eXchanger (MX) Tests
| Status | Test Case | Information |
|---|---|---|
| MX Records | Your Mail eXchanger (MX) records are: 10 mail.protonmail.ch. [TTL=300]<br>20 mailsec.protonmail.ch. [TTL=300]<br> | |
| All nameservers have same MX records | Good! All of your nameservers have the same MX records. | |
| All MX records contain valid hostnames | Good! All of your MX entries have valid hostnames (e.g. are not IPs or invalid domain names). | |
| All MX records use public IP addresses | Good! All of your MX entries have public IP addresses. | |
| MX record is not a CNAME/alias | Good! When querying for your MX records we did not receive a CNAME record as a result. | |
| MX A records are not CNAME's | Good! No CNAME records are present for your MX A records. | |
| Number of MX records | Good! You have more than one MX record. In the event that the primary mail server is down, you have at least one backup that will continue to accept mail! | |
| Duplicate MX A records | Good! No two MX records resolve to the same IP address. | |
| Differing MX A records | Good! You have no different IPs for your MX A records than the DNS server that is authoritative for that hostname. | |
| MX records have reverse DNS entries | Good! All your MX IP addresses have reverse DNS entries. The reverse entries returned were: 128.70.205.185.in-addr.arpa <--> mail.protonmail.ch. 129.42.70.185.in-addr.arpa <--> mailsec.protonmail.ch. |
WWW Record Tests
| Status | Test Case | Information |
|---|---|---|
| WWW record | www.virped.org A records are: www.virped.org. A 104.21.45.133 [TTL=300] www.virped.org. A 172.67.214.165 [TTL=300] | |
| WWW A record has public IP | Good! The IP address(es) of the A records returned for your WWW record have public IP addresses. | |
| WWW CNAME lookup | OK! You don't have a CNAME entry for your WWW record! This is ok though because you have an A record for your WWW record. When people visit www.virped.org they will go to the IP address in the A record above. |
This tool is not currently available via the ViewDNS.info API.