webwiki.de

Checked 22 October 2026, 01:00 UTC · via 8.8.8.8
!Passed with warnings
20 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

ns1.vercel-dns.com, ns2.vercel-dns.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.vercel-dns.com, ns2.vercel-dns.com
NS in the zone
ns1.vercel-dns.com, ns2.vercel-dns.com
NameserverAddressesNetwork (AS)Glue
ns1.vercel-dns.com198.51.44.13 2620:4d:4000:6259:7:13:0:1AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
ns2.vercel-dns.com198.51.45.13 2a00:edc0:6259:7:13::2AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.vercel-dns.com, ns2.vercel-dns.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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS62597 (NSONE - NSONE Inc, 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 .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

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.vercel-dns.com 198.51.44.13NOERROR, 6 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
ns1.vercel-dns.com 2620:4d:4000:6259:7:13:0:1NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
ns2.vercel-dns.com 198.51.45.13NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
ns2.vercel-dns.com 2a00:edc0:6259:7:13::2NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9

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: ns1.vercel-dns.com: "19dd46e347df36b70933bf2be8023258586586a9"; ns2.vercel-dns.com: "19dd46e347df36b70933bf2be8023258586586a9".
    #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 1789553852 · primary ns1.vercel-dns.com

Found

Primary (MNAME)
ns1.vercel-dns.com
Contact (RNAME)
hostmaster.nsone.net
Serial
1789553852
Refresh / retry
43200 s / 7200 s
Expire
1209600 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.vercel-dns.com (198.51.44.13)1789553852
ns1.vercel-dns.com (2620:4d:4000:6259:7:13:0:1)1789553852
ns2.vercel-dns.com (198.51.45.13)1789553852
ns2.vercel-dns.com (2a00:edc0:6259:7:13::2)1789553852

Checks

  • ✓ Serial 1789553852 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 2h, expire 14d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.vercel-dns.com is one of the listed nameservers.
  • ✓ Contact hostmaster@nsone.net #25
    The SOA RNAME hostmaster.nsone.net means hostmaster@nsone.net.
  • ✓ Timestamp serial #26
    The serial 1789553852 is a Unix timestamp (2026-09-16 10:17 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

warn

12 records at the apex

Found

Read from
198.51.44.13:53
TypeValueTTL
SOAns1.vercel-dns.com. hostmaster.nsone.net. 1789553852 43200 7200 1209600 6003600
NSns1.vercel-dns.com.86400
NSns2.vercel-dns.com.86400
A216.150.1.1291800
A216.150.16.1291800
MX10 mx.zoho.eu.60
MX20 mx2.zoho.eu.60
MX50 mx3.zoho.eu.60
TXT"v=spf1 include:zohomail.eu ~all"60
CAA0 issue "letsencrypt.org"60
CAA0 issue "pki.goog"60
CAA0 issue "sectigo.com"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). Low TTLs are useful just before a planned change.
    #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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org, pki.goog, sectigo.com.