buchkatalog.de

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

dns1.cscdns.net, dns2.cscdns.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns1.cscdns.net, dns2.cscdns.net
NS in the zone
dns1.cscdns.net, dns2.cscdns.net
NameserverAddressesNetwork (AS)Glue
dns1.cscdns.net156.154.130.100 2610:a1:1022::100AS12008 VERCARA - Vercara, LLC, US AS12008 VERCARA - Vercara, LLC, US-
dns2.cscdns.net156.154.131.100 2610:a1:1023::100AS12008 VERCARA - Vercara, LLC, US AS12008 VERCARA - Vercara, LLC, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns1.cscdns.net, dns2.cscdns.net.
    #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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS12008 (VERCARA - Vercara, LLC, US): 4 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

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.cscdns.net 156.154.130.100NOERROR, 29 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns1.cscdns.net 2610:a1:1022::100NOERROR, 13 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns2.cscdns.net 156.154.131.100NOERROR, 5 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns2.cscdns.net 2610:a1:1023::100NOERROR, 5 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver

Checks

  • ✓ All respond #14
    All 4 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: dns1.cscdns.net: "UltraDNS Nameserver"; dns2.cscdns.net: "UltraDNS Nameserver".
    #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 2026010904 · primary dns1.cscdns.net

Found

Primary (MNAME)
dns1.cscdns.net
Contact (RNAME)
hostmaster.cscdns.net
Serial
2026010904
Refresh / retry
14400 s / 7200 s
Expire
1209600 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
dns1.cscdns.net (156.154.130.100)2026010904
dns1.cscdns.net (2610:a1:1022::100)2026010904
dns2.cscdns.net (156.154.131.100)2026010904
dns2.cscdns.net (2610:a1:1023::100)2026010904

Checks

  • ✓ Serial 2026010904 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 2h, expire 14d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.cscdns.net is one of the listed nameservers.
  • ✓ Contact hostmaster@cscdns.net #25
    The SOA RNAME hostmaster.cscdns.net means hostmaster@cscdns.net.
  • ✓ Date-based serial #26
    The serial 2026010904 follows the YYYYMMDDnn convention (2026-01-09).

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

warn

12 records at the apex

Found

Read from
156.154.130.100:53
TypeValueTTL
SOAdns1.cscdns.net. hostmaster.cscdns.net. 2026010904 14400 7200 1209600 600600
NSdns1.cscdns.net.600
NSdns2.cscdns.net.600
A20.79.89.1360
MX10 mailgw1.buchkatalog.de.600
MX30 mailgw2.buchkatalog.de.600
TXT"MS=ms49377182"600
TXT"gubmf6l2k1o04mnpt70d439vqd"600
TXT"swisssign-check=Bgtm3-4nlZw4zbXX4fUzQQsSd9M"600
TXT"swisssign-check=ITArv_FbV6tZFOLaNAwAVFl0K44"600
TXT"v=spf1 ip4:194.126.208.179/32 ip4:194.126.208.184/32 include:spf.protection.outlook.com ~all"600
TXT"zone-ownership-verification-705a429c0ac13dd8e6f3b654a2b73dec48617e728dff364aa45dae7d39912a09"600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 10m; resolvers may use either.
    #32
  • ✓ 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