deutschertourismusverband.de

Checked 21 October 2026, 22:13 UTC · via 8.8.8.8
iAll checks passed
26 passed 0 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.nodesecure.com, ns2.nodesecure.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.nodesecure.com, ns2.nodesecure.de
NS in the zone
ns1.nodesecure.com, ns2.nodesecure.de
NameserverAddressesNetwork (AS)Glue
ns1.nodesecure.com192.174.68.102 2001:67c:1bc::102AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns2.nodesecure.de176.97.158.102 2001:67c:10b8::102AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.nodesecure.com, ns2.nodesecure.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
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .de.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.nodesecure.com 192.174.68.102NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.nodesecure.com 2001:67c:1bc::102NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.nodesecure.de 176.97.158.102NOERROR, 13 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.nodesecure.de 2001:67c:10b8::102NOERROR, 13 ms, authoritativenoyes / yesrefusedreg-wie1

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.nodesecure.com: "RcodeZero DNS"; ns2.nodesecure.de: "reg-wie1".
    #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 2026095463 · primary ns1.nodesecure.com

Found

Primary (MNAME)
ns1.nodesecure.com
Contact (RNAME)
domain.pantanet.de
Serial
2026095463
Refresh / retry
43200 s / 7200 s
Expire
1209600 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.nodesecure.com (192.174.68.102)2026095463
ns1.nodesecure.com (2001:67c:1bc::102)2026095463
ns2.nodesecure.de (176.97.158.102)2026095463
ns2.nodesecure.de (2001:67c:10b8::102)2026095463

Checks

  • ✓ Serial 2026095463 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.nodesecure.com is one of the listed nameservers.
  • ✓ Contact domain@pantanet.de #25
    The SOA RNAME domain.pantanet.de means domain@pantanet.de.
  • ✓ Timestamp serial #26
    The serial 2026095463 is a Unix timestamp (2034-03-16 04:17 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
29 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
9192ECDSAP256SHA256 (13)SHA256 CCFA068632B077CA…yes

DNSKEY in the zone

Key tagRoleAlgorithm
33053ZSK (256)ECDSAP256SHA256 (13)
9192KSK (257)ECDSAP256SHA256 (13)

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 9192 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-10-29 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

13 records at the apex

Found

Read from
192.174.68.102:53
TypeValueTTL
SOAns1.nodesecure.com. domain.pantanet.de. 2026095463 43200 7200 1209600 600600
NSns1.nodesecure.com.600
NSns2.nodesecure.de.600
A88.198.180.61600
AAAA2a01:4f8:160:50b7::2600
MX10 mx19a.antispameurope.com.600
MX20 mx19b.antispameurope.com.600
MX30 mx19c.antispameurope.com.600
MX40 mx19d.antispameurope.com.600
TXT"MS=ms14558290"600
TXT"brevo-code:a53e695f8415ffce06a8bc152924739b"600
TXT"google-site-verification=-yxMlwzV4c_-8Egpj_Ip0CU-Q6ZlKYlplfmoLlXknHI"600
TXT"v=spf1 a mx ip4:82.165.38.235 ip4:136.243.134.137 ip4:78.46.68.243 ip4:82.165.192.227 ip6:2001:8d8:8b6:8d00::25:c168 ip6:2a03:2a01:30:89::1:6cb3 include:agenturserver.de include:spf.protection.outlook.com include:antispameurope.com ~all"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, AAAA 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