vkb.de

Checked 22 October 2026, 01:00 UTC · via 8.8.8.8
✗Problems found
18 passed 2 warnings 1 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

ns2.xc-ns.de, ns5.xc-ns.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns2.xc-ns.de, ns5.xc-ns.de
NS in the zone
ns2.xc-ns.de, ns5.xc-ns.de
NameserverAddressesNetwork (AS)Glue
ns2.xc-ns.de193.227.117.225 2a04:2b00:14cc::225AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT193.227.117.225 2a04:2b00:14cc::225
ns5.xc-ns.de194.50.187.225 2a04:2b00:14dd::225AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT194.50.187.225 2a04:2b00:14dd::225

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns2.xc-ns.de, ns5.xc-ns.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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 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 .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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

2 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns2.xc-ns.de 193.227.117.225NOERROR, 6 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.xc-ns.de 2a04:2b00:14cc::225NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns5.xc-ns.de 194.50.187.225no responsenono / no--
ns5.xc-ns.de 2a04:2b00:14dd::225no responsenono / no--

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns5.xc-ns.de (194.50.187.225): read udp 46.225.38.91:48285->194.50.187.225:53: i/o timeout; ns5.xc-ns.de (2a04:2b00:14dd::225): read udp [2a01:4f8:1c1c:eebf::1]:53939->[2a04:2b00:14dd::225]:53: i/o timeout.
    #14
  • ✓ 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: ns2.xc-ns.de: "RcodeZero DNS".
    #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 2026101601 · primary ns2.xc-ns.de

Found

Primary (MNAME)
ns2.xc-ns.de
Contact (RNAME)
domainservice.indeca.de
Serial
2026101601
Refresh / retry
10800 s / 1800 s
Expire
1209600 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns2.xc-ns.de (193.227.117.225)2026101601
ns2.xc-ns.de (2a04:2b00:14cc::225)2026101601

Checks

  • ✓ Serial 2026101601 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 30m, expire 14d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns2.xc-ns.de is one of the listed nameservers.
  • ✓ Contact domainservice@indeca.de #25
    The SOA RNAME domainservice.indeca.de means domainservice@indeca.de.
  • ✓ Date-based serial #26
    The serial 2026101601 follows the YYYYMMDDnn convention (2026-10-16).

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

14 records at the apex

Found

Read from
193.227.117.225:53
TypeValueTTL
SOAns2.xc-ns.de. domainservice.indeca.de. 2026101601 10800 1800 1209600 3003600
NSns2.xc-ns.de.3600
NSns5.xc-ns.de.3600
A212.34.89.1343600
MX30 mailin1.vkb.de.163
MX50 mailin2.vkb.de.163
TXT"apple-domain-verification=oK4a0ixF0wWf5Uqf"3600
TXT"google-gws-recovery-domain-verification=46710027"3600
TXT"facebook-domain-verification=q06ruu6kq2yz5u6jafoviheeaayb9e"3600
TXT"onetrust-domain-verification=9d283f40e8b54bc0991524293d29cbba"3600
TXT"google-site-verification=2jYC3sdxz8lVfk-Wfu4S_SgyPascpX_JcTRa4urEH1w"3600
TXT"google-site-verification=q_H9ER5Xi2ag7bTnYMfGKA1vWWu8kO_6Ux0mJGeRIGo"3600
TXT"cisco-ci-domain-verification=4aad3825e1d7555658d9ce5538d2b1416ff5797e879c7fc940093944d24a755a"3600
TXT"v=spf1 ip4:62.245.172.0/26 ip4:80.243.45.222/32 ip4:185.157.29.16/28 include:_spf.oevcloud.de include:spf.protection.outlook.com ~all"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (2m43s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; 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