ca33pages.de

Checked 21 October 2026, 22:04 UTC · via 8.8.8.8
!Passed with warnings
19 passed 3 warnings 0 failed 7 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

ns.parktons.com, ns2.parktons.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.parktons.com, ns2.parktons.com
NS in the zone
ns.parktons.com, ns2.parktons.com
NameserverAddressesNetwork (AS)Glue
ns.parktons.com46.8.8.88AS60592 GRANSY - Gransy s.r.o., CZ-
ns2.parktons.com46.8.9.99AS60592 GRANSY - Gransy s.r.o., CZ-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.parktons.com, ns2.parktons.com.
    #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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS60592 (GRANSY - Gransy s.r.o., CZ): 2 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 .com
    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

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.parktons.com 46.8.8.88NOERROR, 3 ms, authoritativenoyes / norefused-
ns2.parktons.com 46.8.9.99NOERROR, 3 ms, authoritativenoyes / norefused-

Checks

  • ✓ All respond #14
    All 2 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.
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns.parktons.com (46.8.8.88), ns2.parktons.com (46.8.9.99).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2617179285 · primary ns.parktons.com

Found

Primary (MNAME)
ns.parktons.com
Contact (RNAME)
root.parktons.com
Serial
2617179285
Refresh / retry
86400 s / 7200 s
Expire
1209600 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
ns.parktons.com (46.8.8.88)2617179285
ns2.parktons.com (46.8.9.99)2617179285

Checks

  • ✓ Serial 2617179285 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 14d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.parktons.com is one of the listed nameservers.
  • ✓ Contact root@parktons.com #25
    The SOA RNAME root.parktons.com means root@parktons.com.
  • ✓ Timestamp serial #26
    The serial 2617179285 is a Unix timestamp (2052-12-07 10:14 UTC).

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

13 records at the apex

Found

Read from
46.8.8.88:53
TypeValueTTL
SOAns.parktons.com. root.parktons.com. 2617179285 86400 7200 1209600 18003600
NSns.parktons.com.3600
NSns2.parktons.com.3600
A46.8.8.2203600
A46.8.8.2223600
A46.8.8.2233600
A46.8.8.2243600
A46.8.8.2253600
A46.8.8.2263600
A46.8.8.2273600
A46.8.8.2283600
A46.8.8.2293600
MX10 mail.parktons.com.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