jochen-schweizer.de

Checked 21 October 2026, 23:01 UTC · via 8.8.8.8
!Passed with warnings
21 passed 2 warnings 0 failed 6 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, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.nodesecure.com 2001:67c:1bc::102NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.nodesecure.de 176.97.158.102NOERROR, 11 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.nodesecure.de 2001:67c:10b8::102NOERROR, 11 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

warn

serial 2026102000 · primary ns1.nodesecure.com

Found

Primary (MNAME)
ns1.nodesecure.com
Contact (RNAME)
domreg.cluster-team.com
Serial
2026102000
Refresh / retry
21600 s / 1800 s
Expire
2419200 s
Negative TTL
172800 s

Serial per nameserver

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

Checks

  • ✓ Serial 2026102000 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 6h, retry 30m, expire 28d, negative TTL 2d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.nodesecure.com is one of the listed nameservers.
  • ✓ Contact domreg@cluster-team.com #25
    The SOA RNAME domreg.cluster-team.com means domreg@cluster-team.com.
  • ✓ Date-based serial #26
    The serial 2026102000 follows the YYYYMMDDnn convention (2026-10-20).

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

info

16 records at the apex

Found

Read from
192.174.68.102:53
TypeValueTTL
SOAns1.nodesecure.com. domreg.cluster-team.com. 2026102000 21600 1800 2419200 172800172800
NSns1.nodesecure.com.172800
NSns2.nodesecure.de.172800
A185.157.21.1303600
MX10 mx01.hornetsecurity.com.3600
MX20 mx02.hornetsecurity.com.3600
MX30 mx03.hornetsecurity.com.3600
MX40 mx04.hornetsecurity.com.3600
TXT"MS=ms83639929"300
TXT"3dqgfkj9rfpmrbt34jcywbm2gcrffdfg"300
TXT"7e8bb3599a361c3842f382c6b000a2af"300
TXT"ZOOM_verify_iZQ98c-rTnqOdOTsEPVP7Q"300
TXT"google-site-verification=mDRKiz2J7syErifL49Bc0MFWrMwiizIXAJYQaKa-vTI"300
TXT"T8Bcclzq/mN5o4ZjJiHQWx3I5hAyM9PepqUHgxWmgXYjJXFSzl4mTzhC6YYhpugWgx6MsB/EGgAiQX9f8hWRMw=="300
TXT"rg87a3nppmZCNKNoAvMX5+xgFvFY1t1iDPvx93XtJD9W12og9h5ARl1NOy72s1ue6mmZCq8JpdeYYloeRAK2xA=="300
TXT"v=spf1 mx include:spf.cluster-team.net include:spf.hornetsecurity.com include:spf.protection.outlook.com include:amazonses.com include:iagent-ondemand._spf.novomind.com ip4:188.172.233.148 -all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 2d. The NS TTL at the parent is 1d and in the zone 2d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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