up4dar.de

Checked 22 October 2026, 00:50 UTC · via 8.8.8.8
✗Problems found
17 passed 4 warnings 1 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

fail

ns1.st0ne.net, ns2.st0ne.net, xd.mdx.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.st0ne.net, ns2.st0ne.net, xd.mdx.de
NS in the zone
vhedns1.st0ne.net, vhetzcloud01.st0ne.net
NameserverAddressesNetwork (AS)Glue
ns1.st0ne.net (parent only)188.34.206.181 2a01:4f8:1c1c:3632::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns2.st0ne.net (parent only)116.203.76.65 2a01:4f8:1c1c:b07c::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
vhedns1.st0ne.net (zone only)188.34.206.181 2a01:4f8:1c1c:3632::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
vhetzcloud01.st0ne.net (zone only)116.203.76.65 2a01:4f8:1c1c:b07c::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
xd.mdx.de (parent only)(does not resolve)-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.st0ne.net, ns2.st0ne.net, xd.mdx.de.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.st0ne.net, ns2.st0ne.net, xd.mdx.de; only in the zone: vhedns1.st0ne.net, vhetzcloud01.st0ne.net. ns1.st0ne.net, ns2.st0ne.net, vhedns1.st0ne.net, vhetzcloud01.st0ne.net report NS vhedns1.st0ne.net vhetzcloud01.st0ne.net.
    #7
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✗
    Nameserver names don't resolve
    These nameservers have no A or AAAA record, so they can't be reached (lame delegation): xd.mdx.de.
    #9
  • i
    One address family in one network
    all IPv6 addresses are in 2a01:4f8:1c1c::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ 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

info

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.st0ne.net 188.34.206.181NOERROR, 0 ms, authoritativenoyes / yesrefusedNot today, buddy.
ns1.st0ne.net 2a01:4f8:1c1c:3632::1NOERROR, 0 ms, authoritativenoyes / yesrefusedNot today, buddy.
ns2.st0ne.net 116.203.76.65NOERROR, 0 ms, authoritativenoyes / yesrefusedNot today, buddy.
ns2.st0ne.net 2a01:4f8:1c1c:b07c::1NOERROR, 0 ms, authoritativenoyes / yesrefusedNot today, buddy.
vhedns1.st0ne.net 188.34.206.181NOERROR, 2 ms, authoritativenoyes / yesrefusedNot today, buddy.
vhedns1.st0ne.net 2a01:4f8:1c1c:3632::1NOERROR, 1 ms, authoritativenoyes / yesrefusedNot today, buddy.
vhetzcloud01.st0ne.net 116.203.76.65NOERROR, 3 ms, authoritativenoyes / yesrefusedNot today, buddy.
vhetzcloud01.st0ne.net 2a01:4f8:1c1c:b07c::1NOERROR, 2 ms, authoritativenoyes / yesrefusedNot today, buddy.

Checks

  • ✓ All respond #14
    All 8 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.st0ne.net: "Not today, buddy."; ns2.st0ne.net: "Not today, buddy."; vhedns1.st0ne.net: "Not today, buddy."; vhetzcloud01.st0ne.net: "Not today, buddy.".
    #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 2023030102 · primary vhedns1.st0ne.net

Found

Primary (MNAME)
vhedns1.st0ne.net
Contact (RNAME)
info.st0ne.net
Serial
2023030102
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns1.st0ne.net (188.34.206.181)2023030102
ns1.st0ne.net (2a01:4f8:1c1c:3632::1)2023030102
ns2.st0ne.net (116.203.76.65)2023030102
ns2.st0ne.net (2a01:4f8:1c1c:b07c::1)2023030102
vhedns1.st0ne.net (188.34.206.181)2023030102
vhedns1.st0ne.net (2a01:4f8:1c1c:3632::1)2023030102
vhetzcloud01.st0ne.net (116.203.76.65)2023030102
vhetzcloud01.st0ne.net (2a01:4f8:1c1c:b07c::1)2023030102

Checks

  • ✓ Serial 2023030102 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 3h, retry 1h, expire 7d, negative TTL 3m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver vhedns1.st0ne.net is one of the listed nameservers.
  • ✓ Contact info@st0ne.net #25
    The SOA RNAME info.st0ne.net means info@st0ne.net.
  • ✓ Date-based serial #26
    The serial 2023030102 follows the YYYYMMDDnn convention (2023-03-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

warn

7 records at the apex

Found

Read from
188.34.206.181:53
TypeValueTTL
SOAvhedns1.st0ne.net. info.st0ne.net. 2023030102 10800 3600 604800 18060
NSvhedns1.st0ne.net.60
NSvhetzcloud01.st0ne.net.60
A78.47.41.17460
AAAA2a01:4f8:c0c:2d8a::160
MX0 mail.aignerelektronik.at.60
TXT"v=spf1 a:mail.aignerelektronik.at -all"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (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