Test your DNS server today.

Option - check domain with

Test your DNS server today.

Input zone.tld

Nameservers (up to 30)

Digests

Option - check domain with

What is pre-delegated domain check?

An pre-delegated domain test is a test performed on a domain that can (but need not) be fully published in DNS.

This can be very useful if you are considering moving your domain from one registrar to another. Let us take, for example, the domain example.se being moved from the name server ‘ns.nic.se’ to the name server ‘ns.iis.se’.

In this case, you could run an undelegated domain test on the domain (example.se) with the name server you are moving to (ns.iis.se) BEFORE you go through with the move.

When the test shows green, you can be fairly certain that your domain’s new home is able to answer questions about your domain. However, there may still be errors in the zone data that this test does not know.

nomagic.uk

All is well!

2020-10-31 10:20:29

  • Checked with: IPv4 and IPv6

Link to this result is:
zonemaster.iis.se/?resultid=d7f907d25dd6ca06  |  Copy

Zonemaster lights
SYSTEM
Using version v3.1.2 of the Zonemaster engine.   OK
BASIC
Parent domain 'uk' was found for the tested domain.   OK
IPv6 is enabled, can send "NS" query to ns1.nomagic.fr.   OK
Nameserver ns1.nomagic.fr listed these servers as glue: ns1.nomagic.fr., ns6.gandi.net..   OK
IPv4 is enabled, can send "NS" query to ns1.nomagic.fr.   OK
Nameserver ns1.nomagic.fr listed these servers as glue: ns1.nomagic.fr., ns6.gandi.net..   OK
IPv6 is enabled, can send "NS" query to ns6.gandi.net.   OK
Nameserver ns6.gandi.net listed these servers as glue: ns1.nomagic.fr., ns6.gandi.net..   OK
IPv4 is enabled, can send "NS" query to ns6.gandi.net.   OK
Nameserver ns6.gandi.net listed these servers as glue: ns1.nomagic.fr., ns6.gandi.net..   OK
Functional nameserver found. "A" query for www.nomagic.uk test skipped.   OK
ADDRESS
All Nameserver addresses are in the routable public addressing space.   OK
Reverse DNS entry exists for each Nameserver IP address.   OK
Every reverse DNS entry matches name server name.   OK
CONNECTIVITY
Nameserver ns1.nomagic.fr accessible over UDP on port 53.   OK
Nameserver ns1.nomagic.fr accessible over UDP on port 53.   OK
Nameserver ns6.gandi.net accessible over UDP on port 53.   OK
Nameserver ns6.gandi.net accessible over UDP on port 53.   OK
Nameserver ns1.nomagic.fr accessible over TCP on port 53.   OK
Nameserver ns1.nomagic.fr accessible over TCP on port 53.   OK
Nameserver ns6.gandi.net accessible over TCP on port 53.   OK
Nameserver ns6.gandi.net accessible over TCP on port 53.   OK
Name servers have IPv4 addresses in the following ASs: 29169, 24940.   OK
Name servers have IPv6 addresses in the following ASs: 29169, 24940.   OK
CONNECTIVITY:UNSPECIFIED:NAMESERVERS_IPV4_WITH_MULTIPLE_AS asn=29169, 24940   OK
CONNECTIVITY:UNSPECIFIED:NAMESERVERS_IPV6_WITH_MULTIPLE_AS asn=29169, 24940   OK
CONNECTIVITY:UNSPECIFIED:NAMESERVERS_WITH_MULTIPLE_AS asn=29169, 24940   OK
CONSISTENCY
Saw SOA serial number 2020103100 on following nameserver set : {ns_list}.   OK
A single SOA serial number was found (2020103100).   OK
A single SOA rname value was found (hostmaster.nomagic.uk.).   OK
A single SOA time parameter set was seen (REFRESH=14400, RETRY=3600, EXPIRE=1209600, MINIMUM=3600).   OK
A single NS set was found ({nsname_list}).   OK
Glue records are consistent between glue and authoritative data.   OK
A single SOA mname value was seen (ns1.nomagic.fr.).   OK
DELEGATION
Parent lists enough (2) nameservers ({nsname_list}). Lower limit set to 2.   OK
Child lists enough (2) nameservers ({nsname_list}). Lower limit set to 2.   OK
Child lists enough (2) nameservers ({nsname_list}) that resolve to IPv4 addresses ({ns_ip_list}). Lower limit set to 2.   OK
Child lists enough (2) nameservers ({nsname_list}) that resolve to IPv6 addresses ({ns_ip_list}). Lower limit set to 2.   OK
Delegation lists enough (2) nameservers ({nsname_list}) that resolve to IPv4 addresses ({ns_ip_list}). Lower limit set to 2.   OK
Delegation lists enough (2) nameservers ({nsname_list}) that resolve to IPv6 addresses ({ns_ip_list}). Lower limit set to 2.   OK
All the IP addresses used by the nameservers in parent are unique.   OK
All the IP addresses used by the nameservers in child are unique.   OK
All the IP addresses used by the nameservers are unique.   OK
The smallest possible legal referral packet is smaller than 513 octets (it is 326).   OK
All these nameservers are confirmed to be authoritative : {nsname_list}.   OK
No nameserver points to CNAME alias.   OK
All the nameservers have SOA record.   OK
All of the nameserver names are listed both at parent and child.   OK
DNSSEC
dns1.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
dns1.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
dns1.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
dns1.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
dns2.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
dns2.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
dns2.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
dns2.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
dns3.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
dns3.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
dns3.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
dns3.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
dns4.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
dns4.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
dns4.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
dns4.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
nsa.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
nsa.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
nsa.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
nsa.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
nsb.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
nsb.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
nsc.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
nsc.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
nsd.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 20272 in zone nomagic.uk.   OK
nsd.nic.uk returned a DS record created by algorithm 2 (SHA-256), which is OK. The DS record is for the DNSKEY record with keytag 29314 in zone nomagic.uk.   OK
DNSSEC:UNSPECIFIED:DS_FOUND keytags=29314:20272   OK
DNSSEC:UNSPECIFIED:COMMON_KEYTAGS keytags=20272   OK
DNSSEC:UNSPECIFIED:DS_MATCHES_DNSKEY digtype=2; keytag=20272   OK
DNSSEC:UNSPECIFIED:DS_MATCH_FOUND   OK
RRSIG with keytag 20272 and covering type(s) DNSKEY expires at : Sat Nov 14 04:51:20 2020.   OK
RRSIG with keytag 57189 and covering type(s) SOA expires at : Sat Nov 14 02:35:14 2020.   OK
The DNSKEY with tag 57189 uses algorithm number 8 (RSA/SHA-256), which is OK.   OK
The DNSKEY with tag 20272 uses algorithm number 8 (RSA/SHA-256), which is OK.   OK
The DNSKEY with tag 57189 uses algorithm number 8 (RSA/SHA-256), which is OK.   OK
The DNSKEY with tag 20272 uses algorithm number 8 (RSA/SHA-256), which is OK.   OK
The DNSKEY with tag 57189 uses algorithm number 8 (RSA/SHA-256), which is OK.   OK
The DNSKEY with tag 20272 uses algorithm number 8 (RSA/SHA-256), which is OK.   OK
The DNSKEY with tag 57189 uses algorithm number 8 (RSA/SHA-256), which is OK.   OK
The DNSKEY with tag 20272 uses algorithm number 8 (RSA/SHA-256), which is OK.   OK
The zone has NSEC3 records.   OK
Delegation from parent to child is properly signed.   OK
All the tested RRset (SOA/DNSKEY/NS) are signed by each algorithm present in the DNSKEY RRset.   OK
All keys from the DNSKEY RRset have the correct size.   OK
NAMESERVER
Nameserver ns1.nomagic.fr is not a recursor.   OK
Nameserver ns6.gandi.net is not a recursor.   OK
Nameserver ns1.nomagic.fr is not a recursor.   OK
Nameserver ns6.gandi.net is not a recursor.   OK
The following nameservers support EDNS0 : {ns_list}.   OK
AXFR not available on nameserver ns1.nomagic.fr.   OK
AXFR not available on nameserver ns1.nomagic.fr.   OK
AXFR not available on nameserver ns6.gandi.net.   OK
AXFR not available on nameserver ns6.gandi.net.   OK
All nameservers reply with same IP used to query them.   OK
The following nameservers answer AAAA queries without problems : {ns_list}.   OK
All nameservers succeeded to resolve to an IP address.   OK
None of the following nameservers returns an upward referral : {nsname_list}.   OK
Nameserver ns1.nomagic.fr preserves original case of queried names (WWw.NOMaGic.UK).   OK
Nameserver ns1.nomagic.fr preserves original case of queried names (WWw.NOMaGic.UK).   OK
Nameserver ns6.gandi.net preserves original case of queried names (WWw.NOMaGic.UK).   OK
Nameserver ns6.gandi.net preserves original case of queried names (WWw.NOMaGic.UK).   OK
When asked for SOA records on "www.nomagic.uk" with different cases, all servers reply consistently.   OK
SYNTAX
No illegal characters in the domain name (nomagic.uk).   OK
Neither end of any label in the domain name (nomagic.uk) has a hyphen.   OK
Domain name (nomagic.uk) has no label with a double hyphen ('--') in position 3 and 4 (with a prefix which is not 'xn--').   OK
Nameserver (ns1.nomagic.fr) syntax is valid.   OK
Nameserver (ns6.gandi.net) syntax is valid.   OK
There is no misused '@' character in the SOA RNAME field (hostmaster.nomagic.uk.).   OK
The SOA RNAME field (hostmaster@nomagic.uk) is compliant with RFC2822.   OK
SOA MNAME (ns1.nomagic.fr) syntax is valid.   OK
Domain name MX (courriel1.nomagic.fr) syntax is valid.   OK
Domain name MX (courriel2.nomagic.fr) syntax is valid.   OK
ZONE
SOA 'mname' nameserver (ns1.nomagic.fr) is authoritative for 'nomagic.uk' zone.   OK
SOA 'refresh' value (14400) is greater than the minimum recommended value (14400).   OK
SOA 'refresh' value (14400) is greater than the SOA 'retry' value (3600).   OK
SOA 'retry' value (3600) is greater than the minimum recommended value (3600).   OK
SOA 'expire' value (1209600) is higher than the minimum recommended value (604800) and not lower than the 'refresh' value (14400).   OK
SOA 'minimum' value (3600) is within the recommended ones (300/86400).   OK
SOA 'mname' value (ns1.nomagic.fr) refers to a NS which is not an alias (CNAME).   OK
SOA 'mname' value (ns1.nomagic.fr) refers to a NS which is not an alias (CNAME).   OK
MX record for the domain is not pointing to a CNAME.   OK
MX record for the domain is not pointing to a CNAME.   OK
Target (MX=courriel1.nomagic.fr/ MX=courriel2.nomagic.fr) found to deliver e-mail for the domain name.   OK
A unique SOA record is returned by all nameservers of the zone.   OK
Creation time Overall result
2020-10-31 10:20:29 ( This is current test.)   OK

About Zonemaster

Give your domain a complete physical! Zonemaster helps you to control how your website is doing. As a bonus, you also get a better understanding of how the domain name system, DNS, works.

When a domain (also called zone) is sent to Zonemaster, the program investigates the state of the domain from beginning to end. This is done through Zonemaster examining DNS from the root (.) to the TLD (top-level domain, for example, .se), and then finally through the DNS servers that contain information about the specified domain (for example, zonemaster.se).

Zonemaster is also able to perform many other tests, for example, checking the DNSSEC signatures, that different hosts can be accessed and that the IP addresses are valid. This is all to make sure that your domain runs as good as possible.

About the domain name system, DNS

Most people who use the internet have never reflected over what actually happens when one types an address in their web browser and then clicks the enter button.

To simplify, the domain name system, (DNS) is a database that associates domain names to IP addresses, the same way a phone book associates names to phone numbers.

An IP address is a unique series of numbers that identifies every computer that is connected to the internet. It’s similar to the way every telephone has its own number in the telephone network.

A long series of numbers works fine for computers, but it’s difficult for people to memorize. Therefore, DNS has been developed – an extra system for us when we want to reach a web server on a specific site or an email server we want to send an email to.

Zonemaster all lights