wuerzburg.de

Checked 22 October 2026, 01:02 UTC · via 8.8.8.8
iAll checks passed
27 passed 0 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, 5 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.nodesecure.de 176.97.158.102NOERROR, 12 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 2026104264 · primary ns1.nodesecure.com

Found

Primary (MNAME)
ns1.nodesecure.com
Contact (RNAME)
hostmaster.wuerzburg.de
Serial
2026104264
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

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

Checks

  • ✓ Serial 2026104264 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.nodesecure.com is one of the listed nameservers.
  • ✓ Contact hostmaster@wuerzburg.de #25
    The SOA RNAME hostmaster.wuerzburg.de means hostmaster@wuerzburg.de.
  • ✓ Timestamp serial #26
    The serial 2026104264 is a Unix timestamp (2034-03-16 06:44 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
5 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
8265ECDSAP256SHA256 (13)SHA256 D7B32ECFC8E66C5F…yes

DNSKEY in the zone

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

Records

info

8 records at the apex

Found

Read from
192.174.68.102:53
TypeValueTTL
SOAns1.nodesecure.com. hostmaster.wuerzburg.de. 2026104264 28800 7200 604800 36003600
NSns1.nodesecure.com.3600
NSns2.nodesecure.de.3600
A93.190.71.213600
MX100 mailfilter.regiogate.net.3600
TXT"google-site-verification=L81V_U2U3kNA24mNFHLWzpVIlu3MdrylDe90Fm7Oyvc"3600
TXT"google-site-verification=sjdbIvTR-SPZst082pfYENiBczDuzOSAadXXIQHijDU"3600
TXT"v=spf1 mx a:rgmail.regiogate.net include:spf.mailjet.com include:amazonses.com ~all"3600

Checks

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