dhpv.de

Checked 21 October 2026, 22:14 UTC · via 8.8.8.8
✗Problems found
19 passed 2 warnings 3 failed 5 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.dns1.de, dns.dns2.de, dns.dns3.de, dns.dns4.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns.dns1.de, dns.dns2.de, dns.dns3.de, dns.dns4.de
NS in the zone
dns.dns1.de, dns.dns2.de, dns.dns3.de, dns.dns4.de
NameserverAddressesNetwork (AS)Glue
dns.dns1.de95.130.16.246 2a02:2940:0:a0d1::246AS13246 INETWIRE-AS - Key-Systems GmbH, DE AS13246 INETWIRE-AS - Key-Systems GmbH, DE-
dns.dns2.de95.130.17.218 2a02:2940:0:a0d2::218AS13246 INETWIRE-AS - Key-Systems GmbH, DE AS13246 INETWIRE-AS - Key-Systems GmbH, DE-
dns.dns3.de217.146.22.194 2a00:11c0:e:766::2AS42473 AS-ANEXIA - Anexia Cloud Solutions GmbH, AT AS42473 AS-ANEXIA - Anexia Cloud Solutions GmbH, AT-
dns.dns4.de144.76.91.137 2a01:4f8:192:2187::2AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • ✓ 4 nameservers #6
    Delegated to dns.dns1.de, dns.dns2.de, dns.dns3.de, dns.dns4.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 4 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS13246 (INETWIRE-AS - Key-Systems GmbH, DE): 4 addresses; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS42473 (AS-ANEXIA - Anexia Cloud Solutions GmbH, AT): 2 addresses.
  • 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

7 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns.dns1.de 95.130.16.246no responsenono / no--
dns.dns1.de 2a02:2940:0:a0d1::246NOERROR, 17 ms, authoritativenoyes / yesrefused-
dns.dns2.de 95.130.17.218NOERROR, 10 ms, authoritativeOPENyes / norefused-
dns.dns2.de 2a02:2940:0:a0d2::218NOERROR, 17 ms, authoritativenoyes / yesrefused-
dns.dns3.de 217.146.22.194NOERROR, 3 ms, authoritativenoyes / yesrefused-
dns.dns3.de 2a00:11c0:e:766::2NOERROR, 4 ms, authoritativenoyes / yesrefused-
dns.dns4.de 144.76.91.137NOERROR, 3 ms, authoritativenoyes / yesrefused-
dns.dns4.de 2a01:4f8:192:2187::2NOERROR, 3 ms, authoritativenoyes / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: dns.dns1.de (95.130.16.246): read udp 46.225.38.91:45122->95.130.16.246:53: i/o timeout.
    #14
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: dns.dns2.de (95.130.17.218): NOERROR, authoritative=true.
    #15
  • ✗
    Open recursion
    These nameservers resolve names for anyone, which makes them usable for DNS amplification attacks and cache poisoning: dns.dns2.de (95.130.17.218). Disable recursion on authoritative servers.
    #16
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: dns.dns2.de (95.130.17.218).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2024100201 · primary dns.dns1.de

Found

Primary (MNAME)
dns.dns1.de
Contact (RNAME)
hostmaster.partnergate.com
Serial
2024100201
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
dns.dns1.de (2a02:2940:0:a0d1::246)2024100201
dns.dns2.de (2a02:2940:0:a0d2::218)2024100201
dns.dns3.de (217.146.22.194)2024100201
dns.dns3.de (2a00:11c0:e:766::2)2024100201
dns.dns4.de (144.76.91.137)2024100201
dns.dns4.de (2a01:4f8:192:2187::2)2024100201

Checks

  • ✓ Serial 2024100201 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns.dns1.de is one of the listed nameservers.
  • ✓ Contact hostmaster@partnergate.com #25
    The SOA RNAME hostmaster.partnergate.com means hostmaster@partnergate.com.
  • ✓ Date-based serial #26
    The serial 2024100201 follows the YYYYMMDDnn convention (2024-10-02).

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

9 records at the apex

Found

Read from
[2a02:2940:0:a0d1::246]:53
TypeValueTTL
SOAdns.dns1.de. hostmaster.partnergate.com. 2024100201 28800 7200 604800 8640086400
NSdns.dns3.de.86397
NSdns.dns1.de.86397
NSdns.dns4.de.86397
NSdns.dns2.de.86397
A87.118.90.3286400
MX10 mail.securehost.de.86400
TXT"v=spf1 a include:spf.securehost.de ~all"86400
TXT"MS=ms39055816"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, MX 1d, NS 23h59m57s. The NS TTL at the parent is 1d and in the zone 23h59m57s; 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