domainname.de

Checked 21 October 2026, 22:14 UTC · via 8.8.8.8
!Passed with warnings
17 passed 3 warnings 0 failed 9 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

dns1.domainname.de, dns2.domainname.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns1.domainname.de, dns2.domainname.de
NS in the zone
dns1.domainname.de, dns2.domainname.de
NameserverAddressesNetwork (AS)Glue
dns1.domainname.de144.76.5.119AS24940 HETZNER-AS - Hetzner Online GmbH, DE144.76.5.119
dns2.domainname.de94.130.69.251 2a01:4f8:10b:3350::2AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE94.130.69.251

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns1.domainname.de, dns2.domainname.de.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: dns2.domainname.de (glue 94.130.69.251, zone 94.130.69.251, 2a01:4f8:10b:3350::2). Update the glue at your registrar.
    #8
  • ✓ 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 1 IPv6 /48.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 3 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 .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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: dns1.domainname.de.
    #13

Nameservers

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.domainname.de 144.76.5.119NOERROR, 3 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.8 (built Oct 7 2026 06:11:55 by root@localhost)
dns2.domainname.de 94.130.69.251NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
dns2.domainname.de 2a01:4f8:10b:3350::2NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3

Checks

  • ✓ All respond #14
    All 3 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: dns1.domainname.de: "PowerDNS Authoritative Server 5.0.8 (built Oct 7 2026 06:11:55 by root@localhost)"; dns2.domainname.de: "PowerDNS Authoritative Server 4.7.3". 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

info

serial 2025100201 · primary ns1.info.at

Found

Primary (MNAME)
ns1.info.at
Contact (RNAME)
hostmaster.info.at
Serial
2025100201
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
dns1.domainname.de (144.76.5.119)2025100201
dns2.domainname.de (94.130.69.251)2025100201
dns2.domainname.de (2a01:4f8:10b:3350::2)2025100201

Checks

  • ✓ Serial 2025100201 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1d.
  • i
    Hidden master
    The primary nameserver ns1.info.at 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@info.at #25
    The SOA RNAME hostmaster.info.at means hostmaster@info.at.
  • ✓ Date-based serial #26
    The serial 2025100201 follows the YYYYMMDDnn convention (2025-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

8 records at the apex

Found

Read from
144.76.5.119:53
TypeValueTTL
SOAns1.info.at. hostmaster.info.at. 2025100201 10800 3600 604800 8640086400
NSdns2.domainname.de.86400
NSdns1.domainname.de.86400
A5.9.10.783600
AAAA2a01:4f8:b13:1001::23600
MX10 mail.domainname.de.86400
TXT"google-site-verification=TopL-_HaEv4yA__hGE2FZ4822k1Z75Yhyjm_GNskr8A"86400
TXT"v=spf1 include:spf.mailcenter.at -all"86400

Checks

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