puky.de

Checked 21 October 2026, 23:51 UTC · via 8.8.8.8
!Passed with warnings
18 passed 2 warnings 0 failed 9 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.rheinmedia-dns.de, ns2.rheinmedia-dns.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.rheinmedia-dns.de, ns2.rheinmedia-dns.de
NS in the zone
ns1.rheinmedia-dns.de, ns2.rheinmedia-dns.de
NameserverAddressesNetwork (AS)Glue
ns1.rheinmedia-dns.de45.83.248.122AS203391 CLOUDNSNET - Cloud DNS Ltd, BG45.83.248.122
ns2.rheinmedia-dns.de45.83.249.122AS203391 CLOUDNSNET - Cloud DNS Ltd, BG45.83.249.122

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.rheinmedia-dns.de, ns2.rheinmedia-dns.de.
    #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 (AS203391 (CLOUDNSNET - Cloud DNS Ltd, BG): 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 .de
    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

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.rheinmedia-dns.de 45.83.248.122NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-12
ns2.rheinmedia-dns.de 45.83.249.122NOERROR, 3 ms, authoritativenoyes / yesrefusedde3-12

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.rheinmedia-dns.de: "de3-12"; ns2.rheinmedia-dns.de: "de3-12".
    #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

info

serial 2025121103 · primary ns71.cloudns.net

Found

Primary (MNAME)
ns71.cloudns.net
Contact (RNAME)
support.cloudns.net
Serial
2025121103
Refresh / retry
7200 s / 1800 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.rheinmedia-dns.de (45.83.248.122)2025121103
ns2.rheinmedia-dns.de (45.83.249.122)2025121103

Checks

  • ✓ Serial 2025121103 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 30m, expire 14d, negative TTL 1h.
  • i
    Hidden master
    The primary nameserver ns71.cloudns.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 support@cloudns.net #25
    The SOA RNAME support.cloudns.net means support@cloudns.net.
  • ✓ Date-based serial #26
    The serial 2025121103 follows the YYYYMMDDnn convention (2025-12-11).

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

14 records at the apex

Found

Read from
45.83.248.122:53
TypeValueTTL
SOAns71.cloudns.net. support.cloudns.net. 2025121103 7200 1800 1209600 36003600
NSns1.rheinmedia-dns.de.600
NSns2.rheinmedia-dns.de.600
A49.12.115.54600
MX10 puky-de.mail.protection.outlook.com.600
TXT"_globalsign-domain-verification=yK2lEzs42fYpWQDR7GkC19bl30garj4RyM5niuhjNA"600
TXT"MS=ms79783592"600
TXT"fJ3GKMV+P6HHc88C8VJvnnwFHLiM8LCGYaBUo0blB1WZTYoPOgz/2oRd3omXohiUq4frXTZltNgBO9yMaHbo+A=="600
TXT"brevo-code:31034c962a93f9a4778c158c2cfe896f"600
TXT"v=spf1 include:spf.mailjet.com a mx include:spf1.puky.de include:antispameurope.com include:spf.protection.outlook.com include:spf.cloud.ci-solution.com ~all"600
TXT"klaviyo-site-verification=WAp3Hk"600
TXT"google-site-verification=eVQiKEIf18LZOOgOe07MDD-Izo5pIvusZ-he77ox2wE"600
TXT"klaviyo-site-verification=Vpse7T"600
TXT"sw-domain-hash=5807e7f6c01083592d0e58dfb4543731"600

Checks

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