vzhh.de

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

ns1a.dodns.net, ns2a.dodns.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1a.dodns.net, ns2a.dodns.net
NS in the zone
ns1a.dodns.net, ns2a.dodns.net
NameserverAddressesNetwork (AS)Glue
ns1a.dodns.net217.160.82.254 2001:8d8:fe:53:217:160:82:254AS8560 IONOS-AS - IONOS SE, DE AS8560 IONOS-AS - IONOS SE, DE-
ns2a.dodns.net185.132.35.254 2607:f1c0:fe:53:185:132:35:254AS15418 IONOS-ANYCAST - Fasthosts Internet Limited, GB AS15418 IONOS-ANYCAST - Fasthosts Internet Limited, GB-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1a.dodns.net, ns2a.dodns.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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS15418 (IONOS-ANYCAST - Fasthosts Internet Limited, GB): 2 addresses; AS8560 (IONOS-AS - IONOS SE, DE): 2 addresses.
  • i
    All nameserver names under .net
    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

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1a.dodns.net 217.160.82.254NOERROR, 10 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns1a.dodns.net 2001:8d8:fe:53:217:160:82:254NOERROR, 9 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2a.dodns.net 185.132.35.254NOERROR, 4 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2a.dodns.net 2607:f1c0:fe:53:185:132:35:254NOERROR, 4 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1a.dodns.net: "Served by PowerDNS - https://www.powerdns.com/"; ns2a.dodns.net: "Served by PowerDNS - https://www.powerdns.com/".
    #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 35 · primary ns1.vzhh.de

Found

Primary (MNAME)
ns1.vzhh.de
Contact (RNAME)
hostmaster.vzhh.de
Serial
35
Refresh / retry
86400 s / 10800 s
Expire
3600000 s
Negative TTL
172800 s

Serial per nameserver

NameserverSerial
ns1a.dodns.net (217.160.82.254)35
ns1a.dodns.net (2001:8d8:fe:53:217:160:82:254)35
ns2a.dodns.net (185.132.35.254)35
ns2a.dodns.net (2607:f1c0:fe:53:185:132:35:254)35

Checks

  • ✓ Serial 35 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 3h, expire 1000h, negative TTL 2d.
    #23
  • i
    Hidden master
    The primary nameserver ns1.vzhh.de is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@vzhh.de #25
    The SOA RNAME hostmaster.vzhh.de means hostmaster@vzhh.de.
  • ✓ Counter serial #26
    The serial 35 is a plain counter.

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
217.160.82.254:53
TypeValueTTL
SOAns1.vzhh.de. hostmaster.vzhh.de. 35 86400 10800 3600000 1728003600
NSns1a.dodns.net.3600
NSns2a.dodns.net.3600
A212.224.92.1773600
MX10 vzhh-de.mail.protection.outlook.com.3600
TXT"amazon-business-verification=1d4aa8add58addbeb6099769700ceb9cbf720624f7c9c287488a95139d743986"3600
TXT"MS=7428ADCD6B9482EA0A89C70D525522CB9D12B216"3600
TXT"v=spf1 ip4:212.224.92.177 a:nsp01.buerotec.de a:nsp02.buerotec.de ip4:188.64.58.2 ip4:188.64.58.23 ip4:188.64.58.24 ip4:188.64.58.232 ip4:158.181.48.40 ip4:158.181.48.81 ip4:158.181.48.205 a:mailgateway.terminland.de a:mailgateway2.terminland.de include:s" "pf.protection.outlook.com -all"3600
TXT"google-site-verification=EsawR1RVhroGXh5Zvw0ZU3-fJnlSaXpJkPVJ3DJ8zKk"3600

Checks

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