nuernberger.de

Checked 21 October 2026, 23:40 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

warn

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, ns1.m-online.net, ns2.m-online.net
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
ns1.m-online.net (zone only)212.18.0.8 2001:a60:0:11::53AS8767 MNET-AS - M-net Telekommunikations GmbH, DE AS8767 MNET-AS - M-net Telekommunikations GmbH, DE-
ns2.m-online.net (zone only)212.18.3.8AS8767 MNET-AS - M-net Telekommunikations GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to dns1.odn.de, dns2.odn.de, dns3.odn.de.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns1.m-online.net, ns2.m-online.net. dns1.odn.de, dns2.odn.de, dns3.odn.de, ns1.m-online.net, ns2.m-online.net report NS dns1.odn.de dns2.odn.de dns3.odn.de ns1.m-online.net ns2.m-online.net.
    #7
  • ✓ 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 5 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12348 (AS12348 - ODN OnlineDienst Nordbayern GmbH & Co. KG, DE): 6 addresses; AS8767 (MNET-AS - M-net Telekommunikations GmbH, DE): 3 addresses.
  • 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns2.m-online.net.
    #13

Nameservers

pass

9 of 9 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, 7 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-
ns1.m-online.net 212.18.0.8NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns1.m-online.net 2001:a60:0:11::53NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns2.m-online.net 212.18.3.8NOERROR, 9 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 9 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 2026102101 · primary dns1.odn.de

Found

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

Serial per nameserver

NameserverSerial
dns1.odn.de (212.34.160.53)2026102101
dns1.odn.de (2a01:120:0:101::d1)2026102101
dns2.odn.de (212.34.164.234)2026102101
dns2.odn.de (2a01:120:0:102::d2)2026102101
dns3.odn.de (212.34.166.20)2026102101
dns3.odn.de (2a01:120:0:103::d3)2026102101
ns1.m-online.net (212.18.0.8)2026102101
ns1.m-online.net (2001:a60:0:11::53)2026102101
ns2.m-online.net (212.18.3.8)2026102101

Checks

  • ✓ Serial 2026102101 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 2026102101 follows the YYYYMMDDnn convention (2026-10-21).

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

32 records at the apex

Found

Read from
212.34.160.53:53
TypeValueTTL
SOAdns1.odn.de. hostmaster.odn.de. 2026102101 28800 7200 1209600 360086400
NSdns1.odn.de.300
NSdns3.odn.de.300
NSns2.m-online.net.300
NSns1.m-online.net.300
NSdns2.odn.de.300
A195.60.180.154300
MX10 amx1.nuernberger.de.300
MX10 amx2.nuernberger.de.300
TXT"MS=ms23063375"3600
TXT"google-site-verification=OajjI9EzFsK0FGTqoFkx8QQf3EECaTWMVwKxM2ViAus"3600
TXT"<20.01.2026>"3600
TXT"globalsign-domain-verification=1c9sqXXu-rG7Cq1-JBFw8G9PWklGpInVy3qRvwnyjh"3600
TXT"76bffc5a56fb96553cf8d6946cd1ce3f5c6e45821814ba6e62840cc12370b84f"3600
TXT"MS=ms70435549"3600
TXT"v=spf1 mx ip4:212.34.164.246 ip4:195.60.180.185 ip4:195.60.180.186 ip4:195.60.180.187 ip4:195.60.180.188 include:spf.protection.outlook.com -all"3600
TXT"infoblox-domain-mastery=f194d9232c22b434971cb0c9dd79de2bb97ba4fd12b8c5dc8c24701fc5fb08a2a7"3600
TXT"docker-verification=b629a2e4-384d-4c9f-9f7f-a33f181676d8"3600
TXT"google-site-verification=p8bGbPbvat9gvET0uOGceN7MHF9UG3X-R2jCZu28NvE"3600
TXT"swisssign-check=cxSMPsAgQShK1_nH7G4eUlcWuSo"3600
TXT"google-site-verification=CGUuAxz1wi3VpOp_uxvnwmYWDDY2KpwTGTpodE4voMU"3600
TXT"facebook-domain-verification=ghxbjthckbwe1gsh55ehmlprcepmf6"3600
TXT"swisssign-check=nTJO2g_HwNV6ureXx6codhIgtgY"3600
TXT"swisssign-check=_N19HQoT63L2MG_4F0NOWQeurlE"3600
TXT"globalsign-domain-verification=kiax5zz5JGtRXeA2SJWr5VSDqNcA45egfUIy8m32jh"3600
TXT"google-site-verification=sr_1TMHqMXt__hj6VMmAy5jYBNWDsW7Y8g2q2oKpVew"3600
TXT"apple-domain-verification=Vpz3Hjk2svimegVE"3600
TXT"google-site-verification=q4gcEAkVxkm2ZShIxfAOg-rB70uNLyR3UDqjxD__wus"3600
TXT"atlassian-domain-verification=Z/jAuVgqH9cas/ZhPT9UXLUCYjyn2OHn5b16bcarFRLKBC4WUbw47VAiGCebZAVJ"3600
CAA0 issue "digicert.com"86400
CAA0 issuewild "sectigo.com"86400
CAA0 issue "letsencrypt.org"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 5m. The NS TTL at the parent is 1d and in the zone 5m; 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com, sectigo.com, letsencrypt.org.