kirche-mv.de

Checked 21 October 2026, 23:10 UTC · via 8.8.8.8
✗Problems found
22 passed 3 warnings 1 failed 3 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.toaserver.de, ns1.toaserver.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.toaserver.de, ns1.toaserver.net
NS in the zone
ns1.toaserver.de, ns1.toaserver.net
NameserverAddressesNetwork (AS)Glue
ns1.toaserver.de46.165.212.120AS28753 LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH, DE46.165.212.120
ns1.toaserver.net213.202.216.100AS24961 MYLOC-AS - WIIT AG, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.toaserver.de, ns1.toaserver.net.
    #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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS24961 (MYLOC-AS - WIIT AG, DE): 1 address; AS28753 (LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH, DE): 1 address.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.toaserver.de 46.165.212.120NOERROR, 4 ms, authoritativenoyes / yesrefusedgo away
ns1.toaserver.net 213.202.216.100NOERROR, 9 ms, authoritativenoyes / yesALLOWED (20 records)9.11.3-1ubuntu1.18-Ubuntu

Checks

  • ✓ All respond #14
    All 2 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.toaserver.net: "9.11.3-1ubuntu1.18-Ubuntu". Hide or replace the version string.
    #17
  • ✗
    Zone transfer allowed
    These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns1.toaserver.net (213.202.216.100): 20 records. Restrict zone transfers to your secondary servers.
    #18
  • ✓ 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 2025082012 · primary ns1.toaserver.de

Found

Primary (MNAME)
ns1.toaserver.de
Contact (RNAME)
hostmaster.toaserver.de
Serial
2025082012
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
ns1.toaserver.de (46.165.212.120)2025082012
ns1.toaserver.net (213.202.216.100)2025082012

Checks

  • ✓ Serial 2025082012 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.toaserver.de is one of the listed nameservers.
  • ✓ Contact hostmaster@toaserver.de #25
    The SOA RNAME hostmaster.toaserver.de means hostmaster@toaserver.de.
  • ✓ Date-based serial #26
    The serial 2025082012 follows the YYYYMMDDnn convention (2025-08-20).

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

pass

10 records at the apex

Found

Read from
46.165.212.120:53
TypeValueTTL
SOAns1.toaserver.de. hostmaster.toaserver.de. 2025082012 10800 3600 604800 18001800
NSns1.toaserver.de.1800
NSns1.toaserver.net.1800
A178.162.202.211800
MX20 mx2.toaserver.de.1800
MX10 smtp.toaserver.de.1800
TXT"v=spf1 mx -all"1800
CAA0 issuewild ";"1800
CAA0 iodef "mailto:hostmaster@toaserver.de"1800
CAA0 issue "sectigo.com"1800

Checks

  • ✓ TTLs within range #32
    TTLs: A 30m, MX 30m, NS 30m. The NS TTL at the parent is 1d and in the zone 30m; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: none (issuance forbidden), sectigo.com.