zapatillasconverse.es DNS Report

Health Score: 65%

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

Checked: 1 week before

Parent

NS records at parent servers

dns1.directi.com
dns2.directi.com
[These were obtained from a.nic.es.]

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 directi.com

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (bots416454.earth.orderbox-dns.com,bots416454.mercury.orderbox-dns.com,bots416454.mars.orderbox-dns.com,bots416454.venus.orderbox-dns.com) at nameserver 162.251.82.251
missing A record(s) for (bots416454.earth.orderbox-dns.com,bots416454.mercury.orderbox-dns.com,bots416454.mars.orderbox-dns.com,bots416454.venus.orderbox-dns.com) at nameserver 162.251.82.248

Nameservers report identical NS records 7/7

SUCCESS The NS records at all your nameservers are identical.

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:
bots416454.earth.orderbox-dns.com.
bots416454.mercury.orderbox-dns.com.
bots416454.mars.orderbox-dns.com.
bots416454.venus.orderbox-dns.com.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
dns1.directi.com.
dns2.directi.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
ziyafetwhr.mail.ru
Serial
2018112802
Refresh
7200
Retry
7200
Expire
172800
TTL
7200

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2018112802 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: bots416454.mars.orderbox-dns.com, but that server is not listed at the parent servers.

Serial value 1/1

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

WARNING SOA Expire time is : 172800 seconds. This seems too small. (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 : 7200 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 zapatillasconverse.es
lookup zapatillasconverse.es at A.ROOT-SERVERS.NET(198.41.0.4) 40 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.nic.es(194.69.254.1)
lookup zapatillasconverse.es at a.nic.es(194.69.254.1) 102 ms
a.nic.es(194.69.254.1) refer to dns1.directi.com(unknow IP)
extra IP lookup for dns1.directi.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns1.directi.com at A.ROOT-SERVERS.NET(198.41.0.4) 41 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup dns1.directi.com at a.gtld-servers.net(192.5.6.30) 41 ms
a.gtld-servers.net(192.5.6.30) refer to usc5.akam.net(unknow IP)
extra IP lookup for usc5.akam.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup usc5.akam.net at A.ROOT-SERVERS.NET(198.41.0.4) 41 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup usc5.akam.net at e.gtld-servers.net(192.12.94.30) 23 ms
e.gtld-servers.net(192.12.94.30) refer to a9-67.akam.net(184.85.248.67)
lookup usc5.akam.net at a9-67.akam.net(184.85.248.67) 97 ms
got A record 'usc5.akam.net IN A 96.7.50.65' from usc5.akam.net(184.85.248.67)
lookup dns1.directi.com at usc5.akam.net(96.7.50.65) 64 ms
got A record 'dns1.directi.com IN A 162.251.82.123' from dns1.directi.com(96.7.50.65)
lookup zapatillasconverse.es at dns1.directi.com(162.251.82.123) 46 ms
got A record 'zapatillasconverse.es IN A 91.218.245.171' from zapatillasconverse.es(162.251.82.123)
Total time: 495 ms