deutsche-wirtschafts-nachrichten.de

Checked 21 October 2026, 22:13 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

warn

hydrogen.ns.hetzner.com, oxygen.ns.hetzner.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
hydrogen.ns.hetzner.com, oxygen.ns.hetzner.com
NS in the zone
helium.ns.hetzner.de, hydrogen.ns.hetzner.com, oxygen.ns.hetzner.com
NameserverAddressesNetwork (AS)Glue
helium.ns.hetzner.de (zone only)193.47.99.5 2001:67c:192c::add:5AS12337 NORIS-NETWORK - noris network AG, DE AS12337 NORIS-NETWORK - noris network AG, DE-
hydrogen.ns.hetzner.com213.133.100.98 2a01:4f8:0:1::add:1098AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
oxygen.ns.hetzner.com88.198.229.192 2a01:4f8:0:1::add:2992AS24940 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: hydrogen.ns.hetzner.com, oxygen.ns.hetzner.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: helium.ns.hetzner.de. helium.ns.hetzner.de, hydrogen.ns.hetzner.com, oxygen.ns.hetzner.com report NS helium.ns.hetzner.de hydrogen.ns.hetzner.com oxygen.ns.hetzner.com.
    #7
  • ✓ 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 3 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12337 (NORIS-NETWORK - noris network AG, DE): 2 addresses; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 4 addresses.
  • i
    All nameserver names under .com
    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

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
helium.ns.hetzner.de 193.47.99.5NOERROR, 6 ms, authoritativenoyes / yesrefused-
helium.ns.hetzner.de 2001:67c:192c::add:5NOERROR, 6 ms, authoritativenoyes / yesrefused-
hydrogen.ns.hetzner.com 213.133.100.98NOERROR, 2 ms, authoritativenoyes / yesrefused-
hydrogen.ns.hetzner.com 2a01:4f8:0:1::add:1098NOERROR, 2 ms, authoritativenoyes / yesrefused-
oxygen.ns.hetzner.com 88.198.229.192NOERROR, 1 ms, authoritativenoyes / yesrefused-
oxygen.ns.hetzner.com 2a01:4f8:0:1::add:2992NOERROR, 1 ms, authoritativenoyes / yesrefused-

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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2026042900 · primary ns1.your-server.de

Found

Primary (MNAME)
ns1.your-server.de
Contact (RNAME)
dns.hetzner.com
Serial
2026042900
Refresh / retry
86400 s / 7200 s
Expire
3600000 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
helium.ns.hetzner.de (193.47.99.5)2026042900
helium.ns.hetzner.de (2001:67c:192c::add:5)2026042900
hydrogen.ns.hetzner.com (213.133.100.98)2026042900
hydrogen.ns.hetzner.com (2a01:4f8:0:1::add:1098)2026042900
oxygen.ns.hetzner.com (88.198.229.192)2026042900
oxygen.ns.hetzner.com (2a01:4f8:0:1::add:2992)2026042900

Checks

  • ✓ Serial 2026042900 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 1000h, negative TTL 1h.
  • i
    Hidden master
    The primary nameserver ns1.your-server.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 dns@hetzner.com #25
    The SOA RNAME dns.hetzner.com means dns@hetzner.com.
  • ✓ Date-based serial #26
    The serial 2026042900 follows the YYYYMMDDnn convention (2026-04-29).

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

warn

12 records at the apex

Found

Read from
193.47.99.5:53
TypeValueTTL
SOAns1.your-server.de. dns.hetzner.com. 2026042900 86400 7200 3600000 360060
NShelium.ns.hetzner.de.60
NShydrogen.ns.hetzner.com.60
NSoxygen.ns.hetzner.com.60
A213.239.197.5160
MX5 alt2.aspmx.l.google.com.60
MX1 aspmx.l.google.com.60
MX10 aspmx2.googlemail.com.60
MX10 aspmx3.googlemail.com.60
MX5 alt1.aspmx.l.google.com.60
TXT"google-site-verification=tKXJyEGaHfdDnEaialTmg2vGc8DY0xeNS547sXwJJgA"60
TXT"v=spf1 a mx a:dwn-thor.deutsche-wirtschafts-nachrichten.de ?all"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1m; resolvers may use either.
    #32
  • ✓ 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