home64.de

Checked 21 October 2026, 22:50 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.ipv64.net, ns2.ipv64.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.ipv64.net, ns2.ipv64.net
NS in the zone
ns1.ipv64.net, ns2.ipv64.net
NameserverAddressesNetwork (AS)Glue
ns1.ipv64.net159.69.110.93 2a01:4f8:1c1e:a6a8::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns2.ipv64.net167.235.231.182 2a01:4f8:c010:b4fc::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.ipv64.net, ns2.ipv64.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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 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 .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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.ipv64.net 159.69.110.93NOERROR, 2 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.0-alpha1.688.master.g42244aeae (built Jul 17 2025 11:21:27 by root@localhost)
ns1.ipv64.net 2a01:4f8:1c1e:a6a8::1NOERROR, 2 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.0-alpha1.688.master.g42244aeae (built Jul 17 2025 11:21:27 by root@localhost)
ns2.ipv64.net 167.235.231.182NOERROR, 7 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.0-alpha1.688.master.g42244aeae (built Jul 17 2025 11:21:27 by root@localhost)
ns2.ipv64.net 2a01:4f8:c010:b4fc::1NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.0-alpha1.688.master.g42244aeae (built Jul 17 2025 11:21:27 by root@localhost)

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.ipv64.net: "PowerDNS Authoritative Server 5.0.0-alpha1.688.master.g42244aeae (built Jul 17 2025 11:21:27 by root@localhost)"; ns2.ipv64.net: "PowerDNS Authoritative Server 5.0.0-alpha1.688.master.g42244aeae (built Jul 17 2025 11:21:27 by root@localhost)". 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

warn

serial 2027960869 · primary ns1.ipv64.net

Found

Primary (MNAME)
ns1.ipv64.net
Contact (RNAME)
hostmaster.ipv64.net
Serial
2027960869
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.ipv64.net (159.69.110.93)2027960869
ns1.ipv64.net (2a01:4f8:1c1e:a6a8::1)2027960869
ns2.ipv64.net (167.235.231.182)2027960869
ns2.ipv64.net (2a01:4f8:c010:b4fc::1)2027960867

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2027960867 on ns2.ipv64.net (2a01:4f8:c010:b4fc::1); 2027960869 on ns1.ipv64.net (159.69.110.93), ns1.ipv64.net (2a01:4f8:1c1e:a6a8::1), ns2.ipv64.net (167.235.231.182). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.ipv64.net is one of the listed nameservers.
  • ✓ Contact hostmaster@ipv64.net #25
    The SOA RNAME hostmaster.ipv64.net means hostmaster@ipv64.net.
  • ✓ Timestamp serial #26
    The serial 2027960869 is a Unix timestamp (2034-04-06 18:27 UTC).

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

6 records at the apex

Found

Read from
159.69.110.93:53
TypeValueTTL
SOAns1.ipv64.net. hostmaster.ipv64.net. 2027960869 10800 3600 604800 36003600
NSns2.ipv64.net.3600
NSns1.ipv64.net.3600
A144.76.85.2383600
AAAA2a01:4f8:192:1326::bad:c0de3600
MX10 mail.schroederdennis.de.3600

Checks

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