webcat.info DNS Report

Health Score: 59%

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

Checked: 10 months before


NS records at parent servers

[These were obtained from a2.info.afilias-nst.info.]

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


Mismatched glue 7/7

Skip glue checking. Make sure the nameservers domain is good standing Check yandex.net Check net

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (dns1.yandex.net,dns2.yandex.net) at nameserver

Nameservers report identical NS records 7/7

SUCCESS The NS records at all your nameservers are identical.

Nameservers respond 0/10

Some nameservers does not respond:

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:

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:

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 record

SOA record is:
Hostmaster email

Serial agreement 7/7

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


SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: dns1.yandex.net That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2018032903 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 1/1

SUCCESS SOA Retry interval is : 14400 seconds. This seems OK. (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 1/1

SUCCESS SOA Retry interval is : 900 seconds. This seems OK. (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 : 1209600 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 : 21600 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.


DNS trace

Trace to webcat.info
lookup webcat.info at A.ROOT-SERVERS.NET( 14 ms
A.ROOT-SERVERS.NET( refer to a2.info.afilias-nst.info(
lookup webcat.info at a2.info.afilias-nst.info( 9 ms
a2.info.afilias-nst.info( refer to dns12yandex.net(unknow IP)
extra IP lookup for dns12yandex.net at root server A.ROOT-SERVERS.NET(
lookup dns12yandex.net at A.ROOT-SERVERS.NET( 13 ms
A.ROOT-SERVERS.NET( refer to e.gtld-servers.net(
lookup dns12yandex.net at e.gtld-servers.net( 11 ms
RECORD does not exist
lookup webcat.info at dns12yandex.net() 14 ms
dns12yandex.net() refer to g.root-servers.net(unknow IP)
extra IP lookup for g.root-servers.net at root server A.ROOT-SERVERS.NET(
lookup g.root-servers.net at A.ROOT-SERVERS.NET( 21 ms
got A record 'g.root-servers.net IN A' from g.root-servers.net(
lookup webcat.info at g.root-servers.net( 59 ms
g.root-servers.net( refer to c0.info.afilias-nst.info(
lookup webcat.info at c0.info.afilias-nst.info( 11 ms
c0.info.afilias-nst.info( refer to dns1.yandex.net(unknow IP)
extra IP lookup for dns1.yandex.net at root server A.ROOT-SERVERS.NET(
lookup dns1.yandex.net at A.ROOT-SERVERS.NET( 16 ms
A.ROOT-SERVERS.NET( refer to e.gtld-servers.net(
lookup dns1.yandex.net at e.gtld-servers.net( 23 ms
e.gtld-servers.net( refer to ns9.z5h64q92x9.net(
lookup dns1.yandex.net at ns9.z5h64q92x9.net( 115 ms
got A record 'dns1.yandex.net IN A' from dns1.yandex.net(
lookup webcat.info at dns1.yandex.net( 128 ms
got A record 'webcat.info IN A' from webcat.info(
Total time: 434 ms