teenwhores.me DNS Report

Health Score: 57%

Need help fixing DNS ? Get an expert advise at support forum

Checked: 1 month before

Parent

NS records at parent servers

ns2.brainydns.com
ns1.brainydns.com
[These were obtained from c0.nic.me.]

Glue at parent nameservers 0/7

WARNING The parent servers 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. That may cause some extra milliseconds in DNS. This will usually occur if your DNS servers are not in the same TLD as your domain

NS

Mismatched glue 7/7

Skip glue checking. Make sure the nameservers domain is good standing Check brainydns.com

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.quokkadns.com,ns2.quokkadns.com) at nameserver 5.79.65.14
missing A record(s) for (ns1.domainmx.com,ns2.domainmx.com) at nameserver 104.237.196.114

Nameservers report identical NS records 0/7

The NS records at your nameservers are different
At (5.79.65.14) there are nameservers: ns1.quokkadns.com. ns2.quokkadns.com.
At (104.237.196.114) there are nameservers: ns1.domainmx.com. ns2.domainmx.com.

Nameservers respond 10/10

SUCCESS All of your nameservers listed at the parent nameservers responded.

Nameserver name validity 7/7

SUCCESS All of the NS records that your nameservers report are valid (no IPs or partial domain names).

Number of nameservers 2/5

WARNING You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.

Lame nameservers 7/7

SUCCESS All the nameservers listed at the parent servers answer authoritatively for your domain.

Missing (stealth) nameservers 0/7

DANGER There are nameservers not listed at the parent servers:
ns1.quokkadns.com.
ns2.quokkadns.com.
ns1.domainmx.com.
ns2.domainmx.com.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns2.brainydns.com.
ns1.brainydns.com.

Nameservers on separate class C's 7/7

SUCCESS Nameservers are in a different networks.

public IPs 7/7

SUCCESS All of your NS records appear to use public IPs.

SOA

SOA record

SOA record is:
Hostmaster email
admin.teenwhores.me
Serial
2019022104
Refresh
86400
Retry
10800
Expire
604800
TTL
600

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2019022104 That means that all your nameservers are using the same data.

SOA MNAME 0/3

DANGER SOA (Start of Authority) record states that your master (primary) name server is: ns1.quokkadns.com, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2019022104 This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. This number must be incremented every time you make a DNS change.

Refresh value 0/1

WARNING SOA Retry interval is : 86400 seconds. This seems too big;. (Values 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.

Retry value 0/1

WARNING SOA Retry interval is : 10800 seconds. This seems too big;. (Values 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.

Expire value 1/1

SUCCESS SOA Expire time is : 604800 seconds. This seems OK. (Values 604800 to 2419200 seconds (1-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.

TTL value 1/1

SUCCESS SOA Expire time is : 600 seconds. This seems OK. (about 300 to 86400 seconds or 5 min - 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.

Info

DNS trace

Trace to teenwhores.me
lookup teenwhores.me at A.ROOT-SERVERS.NET(198.41.0.4) 41 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.nic.me(199.253.59.1)
lookup teenwhores.me at a0.nic.me(199.253.59.1) 153 ms
a0.nic.me(199.253.59.1) refer to ns2.brainydns.com(unknow IP)
extra IP lookup for ns2.brainydns.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.brainydns.com at A.ROOT-SERVERS.NET(198.41.0.4) 42 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup ns2.brainydns.com at e.gtld-servers.net(192.12.94.30) 22 ms
e.gtld-servers.net(192.12.94.30) refer to ns-canada.topdns.com(109.201.142.225)
lookup ns2.brainydns.com at ns-canada.topdns.com(109.201.142.225) 83 ms
got A record 'ns2.brainydns.com IN A 5.79.65.14' from ns2.brainydns.com(109.201.142.225)
lookup teenwhores.me at ns2.brainydns.com(5.79.65.14) 89 ms
got A record 'teenwhores.me IN A 37.48.65.154' from teenwhores.me(5.79.65.14)
Total time: 430 ms