ernaehrung.de

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

ns1.nshost2.de, ns2.nshost2.de, ns3.nshost2.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.nshost2.de, ns2.nshost2.de, ns3.nshost2.net
NS in the zone
ns1.nshost2.de, ns2.nshost2.de, ns3.nshost2.net
NameserverAddressesNetwork (AS)Glue
ns1.nshost2.de89.107.184.116 2a01:50c0:1001:1::3:4AS12843 TELEMAXX - TelemaxX Telekommunikation GmbH, DE AS12843 TELEMAXX - TelemaxX Telekommunikation GmbH, DE89.107.184.116
ns2.nshost2.de89.107.185.20 2a01:50c0:1001:1::4:4AS12843 TELEMAXX - TelemaxX Telekommunikation GmbH, DE AS12843 TELEMAXX - TelemaxX Telekommunikation GmbH, DE89.107.185.20
ns3.nshost2.net152.53.140.148 2a0a:4cc0:c1:660:880a:29ff:feb2:ada5AS197540 netcup-AS - netcup GmbH, DE AS197540 netcup-AS - netcup GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.nshost2.de, ns2.nshost2.de, ns3.nshost2.net.
  • ✓ 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: ns1.nshost2.de (glue 89.107.184.116, zone 89.107.184.116, 2a01:50c0:1001:1::3:4); ns2.nshost2.de (glue 89.107.185.20, zone 89.107.185.20, 2a01:50c0:1001:1::4:4). 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 3 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12843 (TELEMAXX - TelemaxX Telekommunikation GmbH, DE): 4 addresses; AS197540 (netcup-AS - netcup GmbH, DE): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.nshost2.de 89.107.184.116NOERROR, 7 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns1.nshost2.de 2a01:50c0:1001:1::3:4NOERROR, 6 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2.nshost2.de 89.107.185.20NOERROR, 6 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.6.4 (built Dec 8 2022 18:40:48 by root@0c326d938171)
ns2.nshost2.de 2a01:50c0:1001:1::4:4NOERROR, 7 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.6.4 (built Dec 8 2022 18:40:48 by root@0c326d938171)
ns3.nshost2.net 152.53.140.148NOERROR, 1 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.0-rc1 (built Sep 29 2022 14:36:11 by root@50c2fba7719c)
ns3.nshost2.net 2a0a:4cc0:c1:660:880a:29ff:feb2:ada5NOERROR, 1 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.0-rc1 (built Sep 29 2022 14:36:11 by root@50c2fba7719c)

Checks

  • ✓ All respond #14
    All 6 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: ns2.nshost2.de: "PowerDNS Authoritative Server 4.6.4 (built Dec 8 2022 18:40:48 by root@0c326d938171)"; ns3.nshost2.net: "PowerDNS Authoritative Server 4.7.0-rc1 (built Sep 29 2022 14:36:11 by root@50c2fba7719c)". 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

pass

serial 2011050116 · primary ns1.nshost2.de

Found

Primary (MNAME)
ns1.nshost2.de
Contact (RNAME)
hostmaster.webhostone.de
Serial
2011050116
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.nshost2.de (89.107.184.116)2011050116
ns1.nshost2.de (2a01:50c0:1001:1::3:4)2011050116
ns2.nshost2.de (89.107.185.20)2011050116
ns2.nshost2.de (2a01:50c0:1001:1::4:4)2011050116
ns3.nshost2.net (152.53.140.148)2011050116
ns3.nshost2.net (2a0a:4cc0:c1:660:880a:29ff:feb2:ada5)2011050116

Checks

  • ✓ Serial 2011050116 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.nshost2.de is one of the listed nameservers.
  • ✓ Contact hostmaster@webhostone.de #25
    The SOA RNAME hostmaster.webhostone.de means hostmaster@webhostone.de.
  • ✓ Date-based serial #26
    The serial 2011050116 follows the YYYYMMDDnn convention (2011-05-01).

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
89.107.184.116:53
TypeValueTTL
SOAns1.nshost2.de. hostmaster.webhostone.de. 2011050116 10800 3600 604800 36003600
NSns1.nshost2.de.3600
NSns2.nshost2.de.3600
NSns3.nshost2.net.3600
A89.107.188.1273600
MX10 mail.ernaehrung.de.3600
TXT"google-site-verification=BvTU8ai72eCJRy72luTYTCRV-pUftASv6hBgvkgIiGw"3600
TXT"v=spf1 ip4:89.107.184.0/21 ip4:185.18.92.0/22 ip4:89.107.188.127 ip6:2a01:50c0::/32 a mx include:spf.serverdomain.org -all"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