lepharaoh.com.de

Zone com.de · Checked 21 October 2026, 23:11 UTC · via 8.8.8.8
!Passed with warnings
24 passed 2 warnings 0 failed 7 info

Registration

info

.de country-code

Found

TLD
.de (country-code)
Public suffix
.com.de
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. Domains are registered under the public suffix .com.de.
    #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.centralnic.net, ns2.centralnic.net, ns3.centralnic.net, ns4.centralnic.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.centralnic.net, ns2.centralnic.net, ns3.centralnic.net, ns4.centralnic.net
NS in the zone
ns1.centralnic.net, ns2.centralnic.net, ns3.centralnic.net, ns4.centralnic.net
NameserverAddressesNetwork (AS)Glue
ns1.centralnic.net194.169.218.24 2001:67c:13cc::1:24AS199330 CENTRALNIC-ANYCAST-A - CentralNic Ltd, GB AS199330 CENTRALNIC-ANYCAST-A - CentralNic Ltd, GB-
ns2.centralnic.net185.24.64.10 2a04:2b00:13cc::1:10AS60890 CENTRALNIC-ANYCAST-B - CentralNic Ltd, GB AS60890 CENTRALNIC-ANYCAST-B - CentralNic Ltd, GB-
ns3.centralnic.net212.18.248.10 2a04:2b00:13ee::10AS201304 CENTRALNIC-ANYCAST-E - CentralNic Ltd, GB AS201304 CENTRALNIC-ANYCAST-E - CentralNic Ltd, GB-
ns4.centralnic.net212.18.249.24 2a04:2b00:13ff::24AS201303 CentralNic-Anycast-F - CentralNic Ltd, GB AS201303 CentralNic-Anycast-F - CentralNic Ltd, GB-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.centralnic.net, ns2.centralnic.net, ns3.centralnic.net, ns4.centralnic.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 4 IPv4 /24s and 4 IPv6 /48s.
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS199330 (CENTRALNIC-ANYCAST-A - CentralNic Ltd, GB): 2 addresses; AS201303 (CentralNic-Anycast-F - CentralNic Ltd, GB): 2 addresses; AS201304 (CENTRALNIC-ANYCAST-E - CentralNic Ltd, GB): 2 addresses; AS60890 (CENTRALNIC-ANYCAST-B - CentralNic Ltd, GB): 2 addresses.
  • 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

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.centralnic.net 194.169.218.24NOERROR, 14 ms, authoritativenoyes / yesrefused-
ns1.centralnic.net 2001:67c:13cc::1:24NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns2.centralnic.net 185.24.64.10NOERROR, 28 ms, authoritativenoyes / yesrefusedoff
ns2.centralnic.net 2a04:2b00:13cc::1:10NOERROR, 23 ms, authoritativenoyes / yesrefusedoff
ns3.centralnic.net 212.18.248.10NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns3.centralnic.net 2a04:2b00:13ee::10NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns4.centralnic.net 212.18.249.24NOERROR, 23 ms, authoritativenoyes / yesrefusedoff
ns4.centralnic.net 2a04:2b00:13ff::24NOERROR, 22 ms, authoritativenoyes / yesrefusedoff

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: ns2.centralnic.net: "off"; ns4.centralnic.net: "off".
    #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 3000601042 · primary ns0.centralnic.net

Found

Primary (MNAME)
ns0.centralnic.net
Contact (RNAME)
hostmaster.centralnic.net
Serial
3000601042
Refresh / retry
900 s / 1800 s
Expire
6048000 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.centralnic.net (194.169.218.24)3000601042
ns1.centralnic.net (2001:67c:13cc::1:24)3000601042
ns2.centralnic.net (185.24.64.10)3000601042
ns2.centralnic.net (2a04:2b00:13cc::1:10)3000601042
ns3.centralnic.net (212.18.248.10)3000601042
ns3.centralnic.net (2a04:2b00:13ee::10)3000601042
ns4.centralnic.net (212.18.249.24)3000601042
ns4.centralnic.net (2a04:2b00:13ff::24)3000601042

Checks

  • ✓ Serial 3000601042 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 15m is outside 20m–1d; retry 30m should be shorter than refresh 15m. Current values: refresh 15m, retry 30m, expire 70d, negative TTL 1h.
    #23
  • i
    Hidden master
    The primary nameserver ns0.centralnic.net 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 hostmaster@centralnic.net #25
    The SOA RNAME hostmaster.centralnic.net means hostmaster@centralnic.net.
  • ✓ Timestamp serial #26
    The serial 3000601042 is a Unix timestamp (2065-01-31 04:17 UTC).

DNSSEC

warn

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
13778RSASHA1-NSEC3-SHA1 (7)SHA256 71D59D06894B670C…NO
13663RSASHA1-NSEC3-SHA1 (7)SHA256 A4AD2831A6853C5C…yes

DNSKEY in the zone

Key tagRoleAlgorithm
37677ZSK (256)RSASHA1-NSEC3-SHA1 (7)
15737ZSK (256)ECDSAP256SHA256 (13)
13663KSK (257)RSASHA1-NSEC3-SHA1 (7)
28371KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • i
    Unused DS records
    These DS records match no key in the zone: key tag 13778 (SHA256). That is normal during a key rollover; otherwise remove them.
    #28
  • !
    Deprecated algorithm
    SHA-1 based algorithms are deprecated and rejected by some validators: RSASHA1-NSEC3-SHA1 (7). Roll over to ECDSAP256SHA256 (13).
    #29
  • ✓ Signatures valid until 2026-11-18 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-18 09:29 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

8 records at the apex

Found

Read from
194.169.218.24:53
TypeValueTTL
SOAns0.centralnic.net. hostmaster.centralnic.net. 3000601042 900 1800 6048000 36003600
NSns4.centralnic.net.3600
NSns1.centralnic.net.3600
NSns3.centralnic.net.3600
NSns2.centralnic.net.3600
A54.153.56.1833600
MX10 mail.cash9.com.3600
TXT"v=spf1 include:googlemail.com ~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