erzbistum-koeln.de

Checked 21 October 2026, 22:19 UTC · via 8.8.8.8
!Passed with warnings
20 passed 3 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

warn

ns1.ntdns.de, ns2.ntdns.de, ns3.ntdns.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.ntdns.de, ns2.ntdns.de, ns3.ntdns.de
NS in the zone
ns1.ntdns.de, ns2.ntdns.de, ns3.ntdns.de
NameserverAddressesNetwork (AS)Glue
ns1.ntdns.de62.141.32.2AS24961 MYLOC-AS - WIIT AG, DE62.141.32.2
ns2.ntdns.de62.141.34.2AS24961 MYLOC-AS - WIIT AG, DE62.141.34.2
ns3.ntdns.de217.79.176.138AS24961 MYLOC-AS - WIIT AG, DE217.79.176.138

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.ntdns.de, ns2.ntdns.de, ns3.ntdns.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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 3 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS24961 (MYLOC-AS - WIIT AG, DE): 3 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.ntdns.de 62.141.32.2NOERROR, 7 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.1
ns2.ntdns.de 62.141.34.2NOERROR, 8 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.1
ns3.ntdns.de 217.79.176.138NOERROR, 7 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.1

Checks

  • ✓ All respond #14
    All 3 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.ntdns.de: "PowerDNS Authoritative Server 4.1.1"; ns2.ntdns.de: "PowerDNS Authoritative Server 4.1.1"; ns3.ntdns.de: "PowerDNS Authoritative Server 4.1.1". Hide or replace the version string.
    #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 2026101501 · primary ns1.ntdns.de

Found

Primary (MNAME)
ns1.ntdns.de
Contact (RNAME)
hostmaster.fastit.net
Serial
2026101501
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.ntdns.de (62.141.32.2)2026101501
ns2.ntdns.de (62.141.34.2)2026101501
ns3.ntdns.de (217.79.176.138)2026101501

Checks

  • ✓ Serial 2026101501 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.ntdns.de is one of the listed nameservers.
  • ✓ Contact hostmaster@fastit.net #25
    The SOA RNAME hostmaster.fastit.net means hostmaster@fastit.net.
  • ✓ Date-based serial #26
    The serial 2026101501 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

info

14 records at the apex

Found

Read from
62.141.32.2:53
TypeValueTTL
SOAns1.ntdns.de. hostmaster.fastit.net. 2026101501 10800 3600 604800 36003600
NSns3.ntdns.de.3600
NSns2.ntdns.de.3600
NSns1.ntdns.de.3600
A208.82.73.212275
MX10 egvmx03.erzbistum-koeln.de.3600
TXT"MS=ms10280204"3600
TXT"/kpyrEOPLBNcTH71ubI8SU7gbGkG0hZ2mCa1OgMp/UfyyJZhox9B/AP9rBFzVq/McSbyGpk3+4iFZSDtnqhkng=="3600
TXT"v=spf1 mx include:_spf.erzbistum-koeln.de include:spf.protection.outlook.com include:spf.crsend.com include:spf-eu.exlibrisgroup.com include:spf.topdesk.net include:_spf.b-ite.com include:spf.brevo.com include:spf.mailjet.com -all"3600
TXT"apple-domain-verification=vdq0YAVS0L0ARCaQ"3600
TXT"google-site-verification=PVwfSlHUAIC9eqL0ILogNdaT7BLX37OGz8Ydjs3s0bE"3600
TXT"google-site-verification=URxHxv3-3Bb-U64xiDKyVWC7PmodqGXAubrg__1HCUg"3600
TXT"ak5tcms0pjag1njyy9st33x8ywolw2"3600
TXT"brevo-code:9c2ca32a3fbbe94013e234e828b15f61"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 37m55s, 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