spielwarenmesse.de

Checked 22 October 2026, 00:23 UTC · via 8.8.8.8
!Passed with warnings
21 passed 2 warnings 0 failed 6 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

dns1.odn.de, dns2.odn.de, dns3.odn.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns1.odn.de, dns2.odn.de, dns3.odn.de
NS in the zone
dns1.odn.de, dns2.odn.de, dns3.odn.de
NameserverAddressesNetwork (AS)Glue
dns1.odn.de212.34.160.53 2a01:120:0:101::d1AS12348 AS12348 - ODN OnlineDienst Nordbayern GmbH & Co. KG, DE AS12348 AS12348 - ODN OnlineDienst Nordbayern GmbH & Co. KG, DE212.34.160.53 2a01:120:0:101::d1
dns2.odn.de212.34.164.234 2a01:120:0:102::d2AS12348 AS12348 - ODN OnlineDienst Nordbayern GmbH & Co. KG, DE AS12348 AS12348 - ODN OnlineDienst Nordbayern GmbH & Co. KG, DE212.34.164.234 2a01:120:0:102::d2
dns3.odn.de212.34.166.20 2a01:120:0:103::d3AS12348 AS12348 - ODN OnlineDienst Nordbayern GmbH & Co. KG, DE AS12348 AS12348 - ODN OnlineDienst Nordbayern GmbH & Co. KG, DE212.34.166.20 2a01:120:0:103::d3

Checks

  • ✓ 3 nameservers #6
    Delegated to dns1.odn.de, dns2.odn.de, dns3.odn.de.
  • ✓ 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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a01:120::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS12348 (AS12348 - ODN OnlineDienst Nordbayern GmbH & Co. KG, DE): 6 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .de
    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
dns1.odn.de 212.34.160.53NOERROR, 1 ms, authoritativenoyes / yesrefused-
dns1.odn.de 2a01:120:0:101::d1NOERROR, 9 ms, authoritativenoyes / yesrefused-
dns2.odn.de 212.34.164.234NOERROR, 1 ms, authoritativenoyes / yesrefused-
dns2.odn.de 2a01:120:0:102::d2NOERROR, 7 ms, authoritativenoyes / yesrefused-
dns3.odn.de 212.34.166.20NOERROR, 1 ms, authoritativenoyes / yesrefused-
dns3.odn.de 2a01:120:0:103::d3NOERROR, 7 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

pass

serial 2026101503 · primary dns1.odn.de

Found

Primary (MNAME)
dns1.odn.de
Contact (RNAME)
hostmaster.odn.de
Serial
2026101503
Refresh / retry
28800 s / 7200 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns1.odn.de (212.34.160.53)2026101503
dns1.odn.de (2a01:120:0:101::d1)2026101503
dns2.odn.de (212.34.164.234)2026101503
dns2.odn.de (2a01:120:0:102::d2)2026101503
dns3.odn.de (212.34.166.20)2026101503
dns3.odn.de (2a01:120:0:103::d3)2026101503

Checks

  • ✓ Serial 2026101503 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.odn.de is one of the listed nameservers.
  • ✓ Contact hostmaster@odn.de #25
    The SOA RNAME hostmaster.odn.de means hostmaster@odn.de.
  • ✓ Date-based serial #26
    The serial 2026101503 follows the YYYYMMDDnn convention (2026-10-15).

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

warn

11 records at the apex

Found

Read from
212.34.160.53:53
TypeValueTTL
SOAdns1.odn.de. hostmaster.odn.de. 2026101503 28800 7200 1209600 360086400
NSdns2.odn.de.3600
NSdns3.odn.de.3600
NSdns1.odn.de.3600
A62.91.43.36240
MX10 mx01.hornetsecurity.com.300
MX20 mx02.hornetsecurity.com.300
TXT"spf2.0/pra"300
TXT"v=spf1 a mx ip4:212.34.165.58 ip4:212.34.165.98 ip4:87.190.28.138 ip4:213.144.20.0/24 ip4:85.115.21.0/24 ip4:91.199.21.0/24 ip4:86.109.253.0/24 ip4:62.157.92.244/28 ip4:80.82.206.0/26 ip4:185.98.184.0/24 mx:indivsurvey.de include:amazonses.com include:spf" ".protection.outlook.com include:spf.hornetsecurity.com include:spf.smtp-engine.com include:_spf.sendnode.com -all"300
TXT"google-site-verification=NWYKP7TSrc2V_L0apB-MTwYelMllwoBwcunurD0B85M"300
TXT"apple-domain-verification=X4FhmPJOuy1bwpKh"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (4m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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