pangaea.de

Checked 21 October 2026, 23:42 UTC · via 8.8.8.8
iAll checks passed
27 passed 0 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.domaindiscount24.net, ns2.domaindiscount24.net, ns3.domaindiscount24.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.domaindiscount24.net, ns2.domaindiscount24.net, ns3.domaindiscount24.net
NS in the zone
ns1.domaindiscount24.net, ns2.domaindiscount24.net, ns3.domaindiscount24.net
NameserverAddressesNetwork (AS)Glue
ns1.domaindiscount24.net193.227.117.34 2a04:2b00:14cc::34AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns2.domaindiscount24.net194.50.187.34 2a04:2b00:14dd::34AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns3.domaindiscount24.net194.0.182.34 2a04:2b00:14ee::34AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.domaindiscount24.net, ns2.domaindiscount24.net, ns3.domaindiscount24.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 3 IPv4 /24s and 3 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 6 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.domaindiscount24.net 193.227.117.34NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.domaindiscount24.net 2a04:2b00:14cc::34NOERROR, 7 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.domaindiscount24.net 194.50.187.34NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.domaindiscount24.net 2a04:2b00:14dd::34NOERROR, 15 ms, authoritativenoyes / yesrefusedreg-wie1
ns3.domaindiscount24.net 194.0.182.34NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns3.domaindiscount24.net 2a04:2b00:14ee::34NOERROR, 7 ms, authoritativenoyes / yesrefusedRcodeZero DNS

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.domaindiscount24.net: "RcodeZero DNS"; ns2.domaindiscount24.net: "reg-wie1"; ns3.domaindiscount24.net: "RcodeZero DNS".
    #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

pass

serial 2026064467 · primary ns1.domaindiscount24.net

Found

Primary (MNAME)
ns1.domaindiscount24.net
Contact (RNAME)
tech.key-systems.net
Serial
2026064467
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
28800 s

Serial per nameserver

NameserverSerial
ns1.domaindiscount24.net (193.227.117.34)2026064467
ns1.domaindiscount24.net (2a04:2b00:14cc::34)2026064467
ns2.domaindiscount24.net (194.50.187.34)2026064467
ns2.domaindiscount24.net (2a04:2b00:14dd::34)2026064467
ns3.domaindiscount24.net (194.0.182.34)2026064467
ns3.domaindiscount24.net (2a04:2b00:14ee::34)2026064467

Checks

  • ✓ Serial 2026064467 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 8h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.domaindiscount24.net is one of the listed nameservers.
  • ✓ Contact tech@key-systems.net #25
    The SOA RNAME tech.key-systems.net means tech@key-systems.net.
  • ✓ Timestamp serial #26
    The serial 2026064467 is a Unix timestamp (2034-03-15 19:41 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
15038ECDSAP256SHA256 (13)SHA256 3B1579038447935D…yes

DNSKEY in the zone

Key tagRoleAlgorithm
39099ZSK (256)ECDSAP256SHA256 (13)
15038KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 15038 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-10-29 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

14 records at the apex

Found

Read from
193.227.117.34:53
TypeValueTTL
SOAns1.domaindiscount24.net. tech.key-systems.net. 2026064467 10800 3600 604800 28800300
NSns1.domaindiscount24.net.300
NSns2.domaindiscount24.net.300
NSns3.domaindiscount24.net.300
A134.1.2.171300
MX10 a3061.mx.srv.dfn.de.300
MX10 b3061.mx.srv.dfn.de.300
MX10 c3061.mx.srv.dfn.de.300
TXT"v=spf1 include:_spf.s3062.mx.srv.dfn.de -all"300
TXT"google-site-verification=OrjQSE-Ie9hPl7CDss6kWcV2heSOJ8Dc8epJ3JSPhw8"300
TXT"cisco-ci-domain-verification=75973c613b7d9abd9c58016b45cd1ab65609d4675908b9a62ab9c1324acc882f"300
CAA0 issue "letsencrypt.org"300
CAA0 issue "pki.dfn.de"300
CAA0 issuewild "letsencrypt.org"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 5m. The NS TTL at the parent is 1d and in the zone 5m; 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org, pki.dfn.de.