ahead.de

Checked 21 October 2026, 21:28 UTC · via 8.8.8.8
✗Problems found
20 passed 3 warnings 1 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

warn

ns.hspeed.net, ns3.hspeed.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.hspeed.net, ns3.hspeed.net
NS in the zone
ns.hspeed.net, ns3.hspeed.net
NameserverAddressesNetwork (AS)Glue
ns.hspeed.net193.24.239.184AS31276 HSPEED-AS - Die Netz-Werker Systemmanagement und Datennetze AG, DE-
ns3.hspeed.net209.126.107.221AS30083 AS-30083-US-VELIA-NET - velia.net, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.hspeed.net, ns3.hspeed.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: AS30083 (AS-30083-US-VELIA-NET - velia.net, DE): 1 address; AS31276 (HSPEED-AS - Die Netz-Werker Systemmanagement und Datennetze AG, DE): 1 address.
  • 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
  • !
    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
ns.hspeed.net 193.24.239.184NOERROR, 10 ms, authoritativenoyes / yesrefused9.20.29-1~deb13u1-Debian
ns3.hspeed.net 209.126.107.221NOERROR, 117 ms, authoritativenoyes / yesALLOWED (13 records)9.18.49-1~deb12u2-Debian

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: ns.hspeed.net: "9.20.29-1~deb13u1-Debian"; ns3.hspeed.net: "9.18.49-1~deb12u2-Debian". 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: ns3.hspeed.net (209.126.107.221): 13 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 2016102403 · primary ns.hspeed.net

Found

Primary (MNAME)
ns.hspeed.net
Contact (RNAME)
hostmaster.hspeed.net
Serial
2016102403
Refresh / retry
10001 s / 1800 s
Expire
2592000 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns.hspeed.net (193.24.239.184)2016102403
ns3.hspeed.net (209.126.107.221)2016102403

Checks

  • ✓ Serial 2016102403 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m41s, retry 30m, expire 30d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.hspeed.net is one of the listed nameservers.
  • ✓ Contact hostmaster@hspeed.net #25
    The SOA RNAME hostmaster.hspeed.net means hostmaster@hspeed.net.
  • ✓ Date-based serial #26
    The serial 2016102403 follows the YYYYMMDDnn convention (2016-10-24).

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

5 records at the apex

Found

Read from
193.24.239.184:53
TypeValueTTL
SOAns.hspeed.net. hostmaster.hspeed.net. 2016102403 10001 1800 2592000 86400600
NSns.hspeed.net.600
NSns3.hspeed.net.600
A193.24.239.209600
MX5 127.0.0.1.ahead.de.600

Checks

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