yigg.de

Checked 22 October 2026, 01:10 UTC · via 8.8.8.8
!Passed with warnings
28 passed 1 warning 0 failed 3 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

pass

ns1.secure-gw.de, ns2.secure-gw.be, ns3.secure-gw.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.secure-gw.de, ns2.secure-gw.be, ns3.secure-gw.de
NS in the zone
ns1.secure-gw.de, ns2.secure-gw.be, ns3.secure-gw.de
NameserverAddressesNetwork (AS)Glue
ns1.secure-gw.de109.235.58.90 2a00:19e0:3002:17fe::7dAS25504 CRONON-AS - Vautron Rechenzentrum AG, DE AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE109.235.58.90 2a00:19e0:3002:17fe::7d
ns2.secure-gw.be152.53.17.164 2a0a:4cc0:1:1a14::2AS197540 netcup-AS - netcup GmbH, DE AS197540 netcup-AS - netcup GmbH, DE-
ns3.secure-gw.de116.202.234.148 2a01:4f8:241:4d96::2000:2AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE116.202.234.148 2a01:4f8:241:4d96::2000:2

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.secure-gw.de, ns2.secure-gw.be, ns3.secure-gw.de.
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS197540 (netcup-AS - netcup GmbH, DE): 2 addresses; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS25504 (CRONON-AS - Vautron Rechenzentrum AG, DE): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .be, .de.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.secure-gw.de 109.235.58.90NOERROR, 20 ms, authoritativenoyes / yesrefused-
ns1.secure-gw.de 2a00:19e0:3002:17fe::7dNOERROR, 20 ms, authoritativenoyes / yesrefused-
ns2.secure-gw.be 152.53.17.164NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns2.secure-gw.be 2a0a:4cc0:1:1a14::2NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns3.secure-gw.de 116.202.234.148NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns3.secure-gw.de 2a01:4f8:241:4d96::2000:2NOERROR, 9 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

pass

serial 2026102296 · primary ns1.secure-gw.de

Found

Primary (MNAME)
ns1.secure-gw.de
Contact (RNAME)
hostmaster.secure-gw.de
Serial
2026102296
Refresh / retry
3600 s / 900 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.secure-gw.de (109.235.58.90)2026102296
ns1.secure-gw.de (2a00:19e0:3002:17fe::7d)2026102296
ns2.secure-gw.be (152.53.17.164)2026102296
ns2.secure-gw.be (2a0a:4cc0:1:1a14::2)2026102296
ns3.secure-gw.de (116.202.234.148)2026102296
ns3.secure-gw.de (2a01:4f8:241:4d96::2000:2)2026102296

Checks

  • ✓ Serial 2026102296 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 15m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.secure-gw.de is one of the listed nameservers.
  • ✓ Contact hostmaster@secure-gw.de #25
    The SOA RNAME hostmaster.secure-gw.de means hostmaster@secure-gw.de.
  • ✓ Date-based serial #26
    The serial 2026102296 follows the YYYYMMDDnn convention (2026-10-22).

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
5 November 2026

DNSKEY in the zone

Key tagRoleAlgorithm
52290ZSK (256)ECDSAP256SHA256 (13)
39323KSK (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 valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 00:14 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

7 records at the apex

Found

Read from
109.235.58.90:53
TypeValueTTL
SOAns1.secure-gw.de. hostmaster.secure-gw.de. 2026102296 3600 900 1209600 36003600
NSns1.secure-gw.de.3600
NSns3.secure-gw.de.3600
NSns2.secure-gw.be.3600
A127.0.0.13600
MX0 .3600
TXT"v=spf1 +mx -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.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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