webador.de

Checked 22 October 2026, 01:00 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)
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

ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
NS in the zone
ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
NameserverAddressesNetwork (AS)Glue
ns-cloud-b1.googledomains.com216.239.32.107 2001:4860:4802:32::6bAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
ns-cloud-b2.googledomains.com216.239.34.107 2001:4860:4802:34::6bAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
ns-cloud-b3.googledomains.com216.239.36.107 2001:4860:4802:36::6bAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
ns-cloud-b4.googledomains.com216.239.38.107 2001:4860:4802:38::6bAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com.
  • ✓ 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.
  • i
    One address family in one network
    all IPv6 addresses are in 2001:4860:4802::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS15169 (GOOGLE - Google LLC, US): 8 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns-cloud-b1.googledomains.com 216.239.32.107NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns-cloud-b1.googledomains.com 2001:4860:4802:32::6bNOERROR, 12 ms, authoritativenoyes / yesrefused-
ns-cloud-b2.googledomains.com 216.239.34.107NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns-cloud-b2.googledomains.com 2001:4860:4802:34::6bNOERROR, 12 ms, authoritativenoyes / yesrefused-
ns-cloud-b3.googledomains.com 216.239.36.107NOERROR, 41 ms, authoritativenoyes / yesrefused-
ns-cloud-b3.googledomains.com 2001:4860:4802:36::6bNOERROR, 42 ms, authoritativenoyes / yesrefused-
ns-cloud-b4.googledomains.com 216.239.38.107NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns-cloud-b4.googledomains.com 2001:4860:4802:38::6bNOERROR, 12 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2 · primary ns-cloud-b1.googledomains.com

Found

Primary (MNAME)
ns-cloud-b1.googledomains.com
Contact (RNAME)
cloud-dns-hostmaster.google.com
Serial
2
Refresh / retry
21600 s / 3600 s
Expire
259200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns-cloud-b1.googledomains.com (216.239.32.107)2
ns-cloud-b1.googledomains.com (2001:4860:4802:32::6b)2
ns-cloud-b2.googledomains.com (216.239.34.107)2
ns-cloud-b2.googledomains.com (2001:4860:4802:34::6b)2
ns-cloud-b3.googledomains.com (216.239.36.107)2
ns-cloud-b3.googledomains.com (2001:4860:4802:36::6b)2
ns-cloud-b4.googledomains.com (216.239.38.107)2
ns-cloud-b4.googledomains.com (2001:4860:4802:38::6b)2

Checks

  • ✓ Serial 2 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    expire 3d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 6h, retry 1h, expire 3d, negative TTL 5m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns-cloud-b1.googledomains.com is one of the listed nameservers.
  • ✓ Contact cloud-dns-hostmaster@google.com #25
    The SOA RNAME cloud-dns-hostmaster.google.com means cloud-dns-hostmaster@google.com.
  • ✓ Counter serial #26
    The serial 2 is a plain counter.

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
1 iterations, 8-byte salt
Signatures valid until
9 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
58271RSASHA256 (8)SHA256 CFD6B507C67078DA…yes

DNSKEY in the zone

Key tagRoleAlgorithm
62031ZSK (256)RSASHA256 (8)
33705ZSK (256)RSASHA256 (8)
58271KSK (257)RSASHA256 (8)

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 58271 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-09 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-09 16:40 UTC.
  • !
    NSEC3 with extra iterations or salt
    NSEC3 uses 1 iteration and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Records

info

15 records at the apex

Found

Read from
216.239.32.107:53
TypeValueTTL
SOAns-cloud-b1.googledomains.com. cloud-dns-hostmaster.google.com. 2 21600 3600 259200 30021600
NSns-cloud-b2.googledomains.com.21600
NSns-cloud-b1.googledomains.com.21600
NSns-cloud-b4.googledomains.com.21600
NSns-cloud-b3.googledomains.com.21600
A34.90.225.19810800
MX10 aspmx3.googlemail.com.10800
MX10 aspmx2.googlemail.com.10800
MX1 aspmx.l.google.com.10800
MX5 alt1.aspmx.l.google.com.10800
MX5 alt2.aspmx.l.google.com.10800
TXT"google-site-verification=-OyKzpSPYlmhDftpuTfWom86ngUc0Q6hcoaapG8rKW0"10800
TXT"google-site-verification=x8EIxKsuUx2cLM8cuYKN61x4UOJi4ziU5-9gnDs5RwM"10800
TXT"facebook-domain-verification=a7tz0xfa3vokoeafgxxkojtuhodfnn"10800
TXT"v=spf1 include:_s00039938.autospf.email include:mail.registrar.eu ~all"10800

Checks

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