bistum-muenster.de

Checked 21 October 2026, 21:47 UTC · via 8.8.8.8
!Passed with warnings
18 passed 3 warnings 0 failed 8 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

dns-2.dfn.de, ns01.bistum-muenster.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns-2.dfn.de, ns01.bistum-muenster.de
NS in the zone
dns-2.dfn.de, ns01.bistum-muenster.de
NameserverAddressesNetwork (AS)Glue
dns-2.dfn.de193.174.75.54 2001:638:d:b102::1AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE-
ns01.bistum-muenster.de195.37.142.85AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE195.37.142.85

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns-2.dfn.de, ns01.bistum-muenster.de.
    #6
  • ✓ 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: ns01.bistum-muenster.de.
  • ✓ 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 1 IPv6 /48.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS680 (DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns01.bistum-muenster.de.
    #13

Nameservers

info

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns-2.dfn.de 193.174.75.54NOERROR, 7 ms, authoritativenoyes / yesrefused0
dns-2.dfn.de 2001:638:d:b102::1NOERROR, 7 ms, authoritativenoyes / yesrefused0
ns01.bistum-muenster.de 195.37.142.85NOERROR, 12 ms, authoritativenoyes / yesrefused-

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: dns-2.dfn.de: "0".
    #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

warn

serial 2026101501 · primary ns01.bistum-muenster.de

Found

Primary (MNAME)
ns01.bistum-muenster.de
Contact (RNAME)
hostmaster.bistum-muenster.de
Serial
2026101501
Refresh / retry
10800 s / 2400 s
Expire
604800 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
dns-2.dfn.de (193.174.75.54)2026101501
dns-2.dfn.de (2001:638:d:b102::1)2026101501
ns01.bistum-muenster.de (195.37.142.85)2026101501

Checks

  • ✓ Serial 2026101501 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 3h, retry 40m, expire 7d, negative TTL 3m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.bistum-muenster.de is one of the listed nameservers.
  • ✓ Contact hostmaster@bistum-muenster.de #25
    The SOA RNAME hostmaster.bistum-muenster.de means hostmaster@bistum-muenster.de.
  • ✓ 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

warn

15 records at the apex

Found

Read from
193.174.75.54:53
TypeValueTTL
SOAns01.bistum-muenster.de. hostmaster.bistum-muenster.de. 2026101501 10800 2400 604800 180180
NSdns-2.dfn.de.180
NSns01.bistum-muenster.de.180
A185.88.213.198180
MX20 bistummuenster-de01e.mail.protection.outlook.com.180
TXT"_globalsign-domain-verification=k3kxIlYurzWjQBjfNKm2flm9n2BYoPkpYIcAZbxNcg"180
TXT"logmein-verification-code=b2f2b091-db20-4e69-add1-b727c2f9c200"180
TXT"cfGtmzwo5IpeNViF2zjBu5mktRd5PWvQ3y4P0Tl8+gXSF1maHqIhniZIBwri0Xox0l6op43FvCFlet4mYFRzIQ=="180
TXT"MS=ms59554514"180
TXT"8ivEmao72/ZVvUWYKdQRcxZik/tqRnnLJuqdBXUf64s="180
TXT"atlassian-domain-verification=VbTOR9sN01jJ6r8aeEMpFMxfSOOL3loOxo7yiCsi8CUX3xzX41zlynEfP22HjCyq"180
TXT"apple-domain-verification=QaSp18CFSlbyH4EV"180
TXT"8If8YlTOISUozLOjeiWXVY5IM/PJ0FIq28R0qWyhtyo12HzBa67vCru4e1yyv+8N4QmMyborh9SQMWBxVdlGeQ=="180
TXT"mindmanager-verification=84960474c23bf89dd38344cf38ba868b2b8599137211838e216a21e78182ee38"180
TXT"v=spf1 ip4:195.37.142.91/32 ip4:195.37.142.92/32 include:spf.protection.outlook.com -all"180

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (3m), MX (3m), NS (3m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 3m; 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