viewdns.info Open in urlscan Pro
2606:4700:20::681a:d76  Public Scan

Form analysis
1 forms found in the DOM

Name: dnsreport — GET

<form name="dnsreport" action="" method="GET" onsubmit="if (!window.__cfRLUnblockHandlers) return false; return validate(this)">
  <font size="2">Domain (<i>e.g. domain.com</i>): <br></font><input name="domain" type="text" size="30"><input type="submit" value="GO">
</form>

Text Content

 * Tools
 * API
 * Research
 * Data

ViewDNS.info > Tools >


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.


Domain (e.g. domain.com):


DNS Report for safnah.com
==============

Parent Nameserver Tests

StatusTest CaseInformationNS records listed at parent serversNameserver records
returned by the parent servers are:

dan.ns.cloudflare.com. [173.245.59.108] [TTL=172800]
tegan.ns.cloudflare.com. [173.245.58.226] [TTL=172800]

This information was kindly provided by a.gtld-servers.net.
Domain listed at parent serversGood! 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 serversGood! The parent servers have your NS
records listed. If they didn't, people wouldn't be able to find your
domain!Parent servers return glueGood! The TLD of your domain (com) matches the
TLD of your nameservers (com) and hence the parent servers MUST return the IP
(glue) for your NS records... AND THEY DO!A record for each NS at parentOops!
The parent servers don't have A records for each of your nameservers! This isn't
a fatal error but means an extra lookup needs to be performed increasing the
load time to your site.


Local Nameserver Tests

StatusTest CaseInformationNS records at your local serversNS records retrieved
from your local nameservers were:

dan.ns.cloudflare.com. [NO GLUE] [TTL=86400]
tegan.ns.cloudflare.com. [NO GLUE] [TTL=86400]
Glue at local nameserversOops! 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 serversHrmm. Either the parent servers or your servers aren't
returning GLUE for your nameservers. This means an extra lookup needs to be
performed to get the IP's of your nameservers.Same NS records at each local
nameserverGood! All your local nameservers have identical NS records for your
domain.Check that all nameservers respondGood! All of your nameservers listed at
the parent servers responded.Check all nameservers are validGood! All of your
nameservers appear to be valid (e.g. are not IP addresses or partial domain
names)Number of nameserversGood! 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 authoritativelyGood! All your nameservers answer
authoritatively for your domain.Missing NS records at parent serversGood! The
parent servers have all the nameservers listed for your domain as your local
nameservers!Missing NS records at local serversGood! Your local servers have all
the nameservers listed for your domain that are listed at the parent servers!No
CNAME records for domainGood! No CNAME records are present for 'safnah.com'.
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
nameserversGood! 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 subnetsGood! All your nameservers are in separate class C
(/24) subnets.Nameservers have public IP'sGood! All your NS records have public
IP addresses.Nameservers allow TCP connectionsGood! 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

StatusTest CaseInformationSOA RecordYour Start of Authority (SOA) record is:

Primary nameserver: dan.ns.cloudflare.com.
Hostmaster E-mail address: dns.cloudflare.com.
Serial number: 2348512536
Refresh: 10000
Retry: 2400
Expire: 604800
Minimum TTL: 1800
All nameservers have same SOA serial numberGood! All your nameservers agree that
your SOA serial number is 2348512536SOA primary nameserver listed at parentGood!
The primary nameserver listed in your SOA record (dan.ns.cloudflare.com.) is
listed at the parent servers!SOA serial number formatOops! Your SOA serial
number (2348512536) 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 valueGood! Your SOA
Refresh value (10000) is within the recommended range of 1 hour (3600) to 1 day
(86400).SOA Retry valueGood! Your SOA Retry value (2400) is within the
recommended range of 5 minutes (300) to 4 hours (14400).SOA Expire valueGood!
Your SOA Expire value (604800) is within the recommended range of 1 week
(604800) to 4 weeks (2419200).SOA Minimum TTL valueGood! Your SOA Minimum TTL
value (1800) is within the recommended range of less than 3 days (259200).


Mail eXchanger (MX) Tests

StatusTest CaseInformationMX RecordsYour Mail eXchanger (MX) records are:

0 _dc-mx.adcacedcc006.safnah.com. [TTL=7200]
All nameservers have same MX recordsGood! All of your nameservers have the same
MX records.All MX records contain valid hostnamesGood! All of your MX entries
have valid hostnames (e.g. are not IP's or invalid domain names).All MX records
use public IP addressesGood! All of your MX entries have public IP addresses.MX
record is not a CNAME/aliasGood! When querying for your MX records we did not
receive a CNAME record as a result.MX A records are not CNAME'sGood! No CNAME
records are present for your MX A records.Number of MX recordsOops! You only
have one MX record! In the event that this mail server is down, you could
potentially lose mail! It is recommended to have two or more MX records (and
hence mail servers) if you want uninterrupted mail functionality.Duplicate MX A
recordsGood! No two MX records resolve to the same IP address.Differing MX A
recordsGood! You have no different IP's for your MX A records than the DNS
server that is authoritive for that hostname.MX records have reverse DNS
entriesGood! All your MX IP addresses have reverse DNS entries. The reverse
entries returned were:

201.194.211.95.in-addr.arpa <--> cp14-nl.temok.com.



WWW Record Tests

StatusTest CaseInformationWWW recordwww.safnah.com A records are:

www.safnah.com. A 104.21.16.22 [TTL=300]
www.safnah.com. A 172.67.165.248 [TTL=300]
WWW A record has public IPGood! The IP address(es) of the A records returned for
your WWW record have public IP addresses.WWW CNAME lookupOK! 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.safnah.com they will go to the IP
address in the A record above.








All content © 2024 ViewDNS.info
Feedback / Suggestions / Contact Us - Privacy Policy