dawum.de

Checked 21 October 2026, 22:12 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 warnings 0 failed 5 info

Registration

info

.de country-code

Found

TLD
.de (country-code)
ICANN policies apply
no

Checks

  • i
    .de is a country-code TLD (ccTLD)
    Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.
    #1
  • ✓ TLD delegated and signed #2
    .de is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .de offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

info

ns1.routing.net, ns2.routing.net, ns3.routing.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.routing.net, ns2.routing.net, ns3.routing.net
NS in the zone
ns1.routing.net, ns2.routing.net, ns3.routing.net
NameserverAddressesNetwork (AS)Glue
ns1.routing.net134.0.30.178 2a03:2900:3:1::2AS48823 AS48823 - Hosting.de GmbH, DE AS48823 AS48823 - Hosting.de GmbH, DE-
ns2.routing.net194.50.113.2 2001:4d8f:2::2AS41637 ROUTING-ANYCAST - Hosting.de GmbH, DE AS41637 ROUTING-ANYCAST - Hosting.de GmbH, DE-
ns3.routing.net194.126.196.2 2a03:2902:3:1::2AS31400 ACCELERATED-IT - firstcolo GmbH, DE AS31400 ACCELERATED-IT - firstcolo GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.routing.net, ns2.routing.net, ns3.routing.net.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS31400 (ACCELERATED-IT - firstcolo GmbH, DE): 2 addresses; AS41637 (ROUTING-ANYCAST - Hosting.de GmbH, DE): 2 addresses; AS48823 (AS48823 - Hosting.de GmbH, DE): 2 addresses.
  • i
    All nameserver names under .net
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.routing.net 134.0.30.178NOERROR, 14 ms, authoritativenoyes / yesrefused-
ns1.routing.net 2a03:2900:3:1::2NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns2.routing.net 194.50.113.2NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.routing.net 2001:4d8f:2::2NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns3.routing.net 194.126.196.2NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3.routing.net 2a03:2902:3:1::2NOERROR, 6 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026101801 · primary ns1.routing.net

Found

Primary (MNAME)
ns1.routing.net
Contact (RNAME)
hostmaster.routing.net
Serial
2026101801
Refresh / retry
3600 s / 3600 s
Expire
86400 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.routing.net (134.0.30.178)2026101801
ns1.routing.net (2a03:2900:3:1::2)2026101801
ns2.routing.net (194.50.113.2)2026101801
ns2.routing.net (2001:4d8f:2::2)2026101801
ns3.routing.net (194.126.196.2)2026101801
ns3.routing.net (2a03:2902:3:1::2)2026101801

Checks

  • ✓ Serial 2026101801 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 1h, expire 1d, negative TTL 5m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.routing.net is one of the listed nameservers.
  • ✓ Contact hostmaster@routing.net #25
    The SOA RNAME hostmaster.routing.net means hostmaster@routing.net.
  • ✓ Date-based serial #26
    The serial 2026101801 follows the YYYYMMDDnn convention (2026-10-18).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

11 records at the apex

Found

Read from
134.0.30.178:53
TypeValueTTL
SOAns1.routing.net. hostmaster.routing.net. 2026101801 3600 3600 86400 3003600
NSns3.routing.net.3600
NSns2.routing.net.3600
NSns1.routing.net.3600
A213.160.75.983600
MX10 mx01.routing.net.3600
MX10 mx02.routing.net.3600
MX10 mx03.routing.net.3600
MX20 mxbackup.routing.net.3600
TXT"google-site-verification=9MdARILNrLhJhNGjogmAwdea93GHO3DVle5sWiZqqRk"3600
TXT"v=spf1 include:spf.routing.net ?all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 1h. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35