sguba.de

Checked 22 October 2026, 00:10 UTC · via 8.8.8.8
!Passed with warnings
24 passed 2 warnings 0 failed 6 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

info

ns1.desec.io, ns2.desec.org

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.desec.io, ns2.desec.org
NS in the zone
ns1.desec.io, ns2.desec.org
NameserverAddressesNetwork (AS)Glue
ns1.desec.io45.54.76.1 2607:f740:e633:deec::2AS63911 NETACTUATE-AS-AP - NetActuate, Inc, US AS63911 NETACTUATE-AS-AP - NetActuate, Inc, US-
ns2.desec.org157.53.224.1 2607:f740:e00a:deec::2AS36217 IRONPATH - NetActuate, Inc, US AS36217 IRONPATH - NetActuate, Inc, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.desec.io, ns2.desec.org.
    #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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS36217 (IRONPATH - NetActuate, Inc, US): 2 addresses; AS63911 (NETACTUATE-AS-AP - NetActuate, Inc, US): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .io, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.desec.io 45.54.76.1NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns1.desec.io 2607:f740:e633:deec::2NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.desec.org 157.53.224.1NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns2.desec.org 2607:f740:e00a:deec::2NOERROR, 10 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 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 2026104666 · primary get.desec.io

Found

Primary (MNAME)
get.desec.io
Contact (RNAME)
get.desec.io
Serial
2026104666
Refresh / retry
86400 s / 3600 s
Expire
2419200 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.desec.io (45.54.76.1)2026104666
ns1.desec.io (2607:f740:e633:deec::2)2026104666
ns2.desec.org (157.53.224.1)2026104666
ns2.desec.org (2607:f740:e00a:deec::2)2026104666

Checks

  • ✓ Serial 2026104666 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 1h, expire 28d, negative TTL 1h.
  • i
    Hidden master
    The primary nameserver get.desec.io 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 get@desec.io #25
    The SOA RNAME get.desec.io means get@desec.io.
  • ✓ Timestamp serial #26
    The serial 2026104666 is a Unix timestamp (2034-03-16 06:51 UTC).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
29 October 2026

DNSKEY in the zone

Key tagRoleAlgorithm
4944KSK (257)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • !
    Signatures expire soon
    The earliest signature expires at 2026-10-29 00:00 UTC (in 168h0m0s). Check that automatic re-signing works.
    #30
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

5 records at the apex

Found

Read from
45.54.76.1:53
TypeValueTTL
SOAget.desec.io. get.desec.io. 2026104666 86400 3600 2419200 3600300
NSns1.desec.io.3600
NSns2.desec.org.3600
A207.180.250.1143600
MX10 mail.sguba.de.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