erzbistum-muenchen.de

Checked 21 October 2026, 22:19 UTC · via 8.8.8.8
iAll checks passed
26 passed 0 warnings 0 failed 7 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.nic53.net, ns2.nic53.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.nic53.net, ns2.nic53.de
NS in the zone
ns1.nic53.net, ns2.nic53.de
NameserverAddressesNetwork (AS)Glue
ns1.nic53.net192.174.68.103 2001:67c:1bc::103AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns2.nic53.de176.97.158.103 2001:67c:10b8::103AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.nic53.net, ns2.nic53.de.
    #6
  • ✓ 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 2 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.nic53.net 192.174.68.103NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.nic53.net 2001:67c:1bc::103NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.nic53.de 176.97.158.103NOERROR, 13 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.nic53.de 2001:67c:10b8::103NOERROR, 13 ms, authoritativenoyes / yesrefusedreg-wie1

Checks

  • ✓ All respond #14
    All 4 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.nic53.net: "RcodeZero DNS"; ns2.nic53.de: "reg-wie1".
    #17
  • ✓ 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 1787648686 · primary ns1.nic53.net

Found

Primary (MNAME)
ns1.nic53.net
Contact (RNAME)
hostmaster.nicmanager.com
Serial
1787648686
Refresh / retry
14400 s / 1800 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.nic53.net (192.174.68.103)1787648686
ns1.nic53.net (2001:67c:1bc::103)1787648686
ns2.nic53.de (176.97.158.103)1787648686
ns2.nic53.de (2001:67c:10b8::103)1787648686

Checks

  • ✓ Serial 1787648686 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 30m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.nic53.net is one of the listed nameservers.
  • ✓ Contact hostmaster@nicmanager.com #25
    The SOA RNAME hostmaster.nicmanager.com means hostmaster@nicmanager.com.
  • ✓ Timestamp serial #26
    The serial 1787648686 is a Unix timestamp (2026-08-25 09:04 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
29 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
63022ECDSAP256SHA256 (13)SHA256 4AD6EB4123403112…yes

DNSKEY in the zone

Key tagRoleAlgorithm
1418ZSK (256)ECDSAP256SHA256 (13)
38693ZSK (256)ECDSAP256SHA256 (13)
63022KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 63022 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-10-29 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

9 records at the apex

Found

Read from
192.174.68.103:53
TypeValueTTL
SOAns1.nic53.net. hostmaster.nicmanager.com. 1787648686 14400 1800 1209600 360086400
NSns1.nic53.net.3600
NSns2.nic53.de.3600
A80.190.116.106900
MX10 mx02.dioezesennetz.de.1800
MX20 mx01.dioezesennetz.de.1800
TXT"MS=ms96796941"1800
TXT"OKKBtGp6XOldn0_h-51W"1800
TXT"v=spf1 include:_spf.dioezesennetz.de -all"1800

Checks

  • ✓ TTLs within range #32
    TTLs: A 15m, MX 30m, 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