muenchen.de

Checked 21 October 2026, 23:30 UTC · via 8.8.8.8
!Passed with warnings
22 passed 1 warning 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

ns01e.muenchen.de, ns02e.muenchen.de, ns05e.muenchen.de, ns06e.muenchen.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns01e.muenchen.de, ns02e.muenchen.de, ns05e.muenchen.de, ns06e.muenchen.de
NS in the zone
ns01e.muenchen.de, ns02e.muenchen.de, ns05e.muenchen.de, ns06e.muenchen.de
NameserverAddressesNetwork (AS)Glue
ns01e.muenchen.de194.246.140.196 2a02:102e:f::a001AS24845 LHM-AS - Landeshauptstadt Muenchen, it@M, DE AS24845 LHM-AS - Landeshauptstadt Muenchen, it@M, DE194.246.140.196 2a02:102e:f::a001
ns02e.muenchen.de194.246.140.219 2a02:102e:f::b001AS24845 LHM-AS - Landeshauptstadt Muenchen, it@M, DE AS24845 LHM-AS - Landeshauptstadt Muenchen, it@M, DE194.246.140.219 2a02:102e:f::b001
ns05e.muenchen.de194.113.41.238AS203989 LHM-PAED - Landeshauptstadt Muenchen, it@M, DE194.113.41.238
ns06e.muenchen.de194.113.41.239AS203989 LHM-PAED - Landeshauptstadt Muenchen, it@M, DE194.113.41.239

Checks

  • ✓ 4 nameservers #6
    Delegated to ns01e.muenchen.de, ns02e.muenchen.de, ns05e.muenchen.de, ns06e.muenchen.de.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns01e.muenchen.de, ns02e.muenchen.de, ns05e.muenchen.de, ns06e.muenchen.de.
  • ✓ 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 2a02:102e:f::/48, while the other address family is spread over several networks.
    #10
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS203989 (LHM-PAED - Landeshauptstadt Muenchen, it@M, DE): 2 addresses; AS24845 (LHM-AS - Landeshauptstadt Muenchen, it@M, DE): 4 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: ns05e.muenchen.de, ns06e.muenchen.de.
    #13

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns01e.muenchen.de 194.246.140.196NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns01e.muenchen.de 2a02:102e:f::a001NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns02e.muenchen.de 194.246.140.219NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns02e.muenchen.de 2a02:102e:f::b001NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns05e.muenchen.de 194.113.41.238NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns06e.muenchen.de 194.113.41.239NOERROR, 10 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 2020073703 · primary ns01e.muenchen.de

Found

Primary (MNAME)
ns01e.muenchen.de
Contact (RNAME)
lhm-zone-c.muenchen.de
Serial
2020073703
Refresh / retry
10800 s / 1800 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns01e.muenchen.de (194.246.140.196)2020073703
ns01e.muenchen.de (2a02:102e:f::a001)2020073703
ns02e.muenchen.de (194.246.140.219)2020073703
ns02e.muenchen.de (2a02:102e:f::b001)2020073703
ns05e.muenchen.de (194.113.41.238)2020073703
ns06e.muenchen.de (194.113.41.239)2020073703

Checks

  • ✓ Serial 2020073703 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 30m, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01e.muenchen.de is one of the listed nameservers.
  • ✓ Contact lhm-zone-c@muenchen.de #25
    The SOA RNAME lhm-zone-c.muenchen.de means lhm-zone-c@muenchen.de.
  • ✓ Timestamp serial #26
    The serial 2020073703 is a Unix timestamp (2034-01-05 11:35 UTC).

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

26 records at the apex

Found

Read from
194.246.140.196:53
TypeValueTTL
SOAns01e.muenchen.de. lhm-zone-c.muenchen.de. 2020073703 10800 1800 604800 8640086400
NSns06e.muenchen.de.86400
NSns02e.muenchen.de.86400
NSns01e.muenchen.de.86400
NSns05e.muenchen.de.86400
A151.101.66.21686400
A151.101.2.21686400
A151.101.130.21686400
A151.101.194.21686400
MX10 esavvfp103.muenchen.de.3600
MX10 esavvfp104.muenchen.de.3600
MX10 c119-k30-rz.muenchen.de.3600
MX10 c118-k30-rz.muenchen.de.3600
MX10 c119-apb20-rz.muenchen.de.3600
MX10 c118-apb20-rz.muenchen.de.3600
MX10 esavvfp101.muenchen.de.3600
MX10 esavvfp102.muenchen.de.3600
TXT"v=spf1 mx -all"3600
TXT"autodesk-domain-verification=RbsfHJczy8cBcWkf4H-o"3600
TXT"cisco-ci-domain-verification=5030c92bf8abac49dd887044afeadf11e92869b8ecab91841f00992256f7f01b"3600
TXT"adobe-idp-site-verification=dbeb15ad8215ac516675b24c31c517959f86d79f7be136450cb14dfb1675e43e"3600
TXT"cisco-ci-domain-verification=20c21e579e7e935cd3e7196cba7a9b9a39b6aecf3b24eafb8816ae5a45824174"3600
TXT"duo_sso_verification=l0uwhvzaIwFcrHAaoGFRCgJiX5fsCiuv9IxapkycYw5exwQ374bzPdp3QhJ5QjAX"3600
TXT"apple-domain-verification=MNANb2lcdzz6d6SE"3600
TXT"successfactors-site-verification=NDk2Y2FlMGE0NzFhOTBiMjdkOWQ5ZDQzYzk1MTYwOGU3NjZmY2YwNDRlYjFkZWE2ZTU5MmMyMWQzOWI3NjdmNQ=="3600
TXT"ms-domain-verification=27c5e1fb-f933-4050-b220-c23c76fddbbc"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, MX 1h, NS 1d.
  • ✓ 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