diekfzgutachterwestfalen.de

Checked 21 October 2026, 22:14 UTC · via 8.8.8.8
!Passed with warnings
19 passed 3 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.dns-parking.com, ns2.dns-parking.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.dns-parking.com, ns2.dns-parking.com
NS in the zone
ns1.dns-parking.com, ns2.dns-parking.com
NameserverAddressesNetwork (AS)Glue
ns1.dns-parking.com162.159.24.201 2400:cb00:2049:1::a29f:18c9AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
ns2.dns-parking.com162.159.25.42 2400:cb00:2049:1::a29f:192aAS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.dns-parking.com, ns2.dns-parking.com.
    #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.
  • i
    One address family in one network
    all IPv6 addresses are in 2400:cb00:2049::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 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
  • i
    All nameserver names under .com
    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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.dns-parking.com 162.159.24.201NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.8
ns1.dns-parking.com 2400:cb00:2049:1::a29f:18c9NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.8
ns2.dns-parking.com 162.159.25.42NOERROR, 111 ms, authoritativenoyes / yesrefused2026.10.8
ns2.dns-parking.com 2400:cb00:2049:1::a29f:192aNOERROR, 180 ms, authoritativenoyes / yesrefused2026.10.8

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.dns-parking.com: "2026.10.8"; ns2.dns-parking.com: "2026.10.8". 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.dns-parking.com

Found

Primary (MNAME)
ns1.dns-parking.com
Contact (RNAME)
dns.hostinger.com
Serial
2026101501
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.dns-parking.com (162.159.24.201)2026101501
ns1.dns-parking.com (2400:cb00:2049:1::a29f:18c9)2026101501
ns2.dns-parking.com (162.159.25.42)2026101501
ns2.dns-parking.com (2400:cb00:2049:1::a29f:192a)2026101501

Checks

  • ✓ Serial 2026101501 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.dns-parking.com is one of the listed nameservers.
  • ✓ Contact dns@hostinger.com #25
    The SOA RNAME dns.hostinger.com means dns@hostinger.com.
  • ✓ 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

11 records at the apex

Found

Read from
162.159.24.201:53
TypeValueTTL
SOAns1.dns-parking.com. dns.hostinger.com. 2026101501 10000 2400 604800 6003600
NSns1.dns-parking.com.86400
NSns2.dns-parking.com.86400
A92.113.16.11360
A92.113.23.23760
AAAA2a02:4780:43:521e:a62a:6156:c6ec:370660
AAAA2a02:4780:42:2895:1c30:9873:f8bf:157260
MX10 mx2.hostinger.com.14400
MX5 mx1.hostinger.com.14400
TXT"v=spf1 include:_spf.mail.hostinger.com ~all"14400
TXT"google-site-verification=eUDHJaOU3BbbEJOzUy8WohNNhjK6xHEaP_MO1Pa-UA0"14400

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m). Low TTLs are useful just before a planned change.
    #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