kanalidee.de

Checked 21 October 2026, 23:02 UTC · via 8.8.8.8
✗Problems found
20 passed 2 warnings 1 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

warn

ns1.regery.net, ns2.regery.net, ns3.regery.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.regery.net, ns2.regery.net, ns3.regery.net
NS in the zone
ns1.regery.net, ns2.regery.net, ns3.regery.net
NameserverAddressesNetwork (AS)Glue
ns1.regery.net136.243.218.113AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns2.regery.net136.243.218.114AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns3.regery.net116.202.42.237AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.regery.net, ns2.regery.net, ns3.regery.net.
  • ✓ 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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 3 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .net
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.regery.net 136.243.218.113NOERROR, 3 ms, authoritativenono / yesrefused-
ns2.regery.net 136.243.218.114NOERROR, 3 ms, authoritativenono / yesrefused-
ns3.regery.net 116.202.42.237NOERROR, 3 ms, authoritativenono / yesrefused-

Checks

  • ✓ All respond #14
    All 3 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.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.regery.net (136.243.218.113): dial tcp 136.243.218.113:53: i/o timeout; ns2.regery.net (136.243.218.114): dial tcp 136.243.218.114:53: i/o timeout; ns3.regery.net (116.202.42.237): dial tcp 116.202.42.237:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2025121530 · primary ns1.regery.net

Found

Primary (MNAME)
ns1.regery.net
Contact (RNAME)
support.regery.com
Serial
2025121530
Refresh / retry
86400 s / 10800 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.regery.net (136.243.218.113)2025121530
ns2.regery.net (136.243.218.114)2025121530
ns3.regery.net (116.202.42.237)2025121530

Checks

  • ✓ Serial 2025121530 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 3h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.regery.net is one of the listed nameservers.
  • ✓ Contact support@regery.com #25
    The SOA RNAME support.regery.com means support@regery.com.
  • ✓ Date-based serial #26
    The serial 2025121530 follows the YYYYMMDDnn convention (2025-12-15).

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

5 records at the apex

Found

Read from
136.243.218.113:53
TypeValueTTL
SOAns1.regery.net. support.regery.com. 2025121530 86400 10800 604800 36003594
NSns1.regery.net.3594
NSns3.regery.net.3594
NSns2.regery.net.3594
A84.247.139.283600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, NS 59m54s. The NS TTL at the parent is 1d and in the zone 59m54s; 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