soscisurvey.de

Checked 22 October 2026, 00:23 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

anycast.regdns1.de, anycast.regdns2.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
anycast.regdns1.de, anycast.regdns2.net
NS in the zone
anycast.regdns1.de, anycast.regdns2.net
NameserverAddressesNetwork (AS)Glue
anycast.regdns1.de192.174.68.100 2001:67c:1bc::100AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT192.174.68.100 2001:67c:1bc::100
anycast.regdns2.net176.97.158.100 2001:67c:10b8::100AS1921 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: anycast.regdns1.de, anycast.regdns2.net.
    #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 .de, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
anycast.regdns1.de 192.174.68.100NOERROR, 7 ms, authoritativenoyes / yesrefusedRcodeZero DNS
anycast.regdns1.de 2001:67c:1bc::100NOERROR, 7 ms, authoritativenoyes / yesrefusedRcodeZero DNS
anycast.regdns2.net 176.97.158.100NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1
anycast.regdns2.net 2001:67c:10b8::100NOERROR, 12 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: anycast.regdns1.de: "RcodeZero DNS"; anycast.regdns2.net: "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 2025115968 · primary anycast.regdns1.de

Found

Primary (MNAME)
anycast.regdns1.de
Contact (RNAME)
hostmaster.partnergate.com
Serial
2025115968
Refresh / retry
7200 s / 3600 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
anycast.regdns1.de (192.174.68.100)2025115968
anycast.regdns1.de (2001:67c:1bc::100)2025115968
anycast.regdns2.net (176.97.158.100)2025115968
anycast.regdns2.net (2001:67c:10b8::100)2025115968

Checks

  • ✓ Serial 2025115968 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 1h, expire 7d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver anycast.regdns1.de is one of the listed nameservers.
  • ✓ Contact hostmaster@partnergate.com #25
    The SOA RNAME hostmaster.partnergate.com means hostmaster@partnergate.com.
  • ✓ Timestamp serial #26
    The serial 2025115968 is a Unix timestamp (2034-03-04 20:12 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
60250RSASHA256 (8)SHA256 E37105678713439F…yes

DNSKEY in the zone

Key tagRoleAlgorithm
10879ZSK (256)RSASHA256 (8)
60250KSK (257)RSASHA256 (8)

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 60250 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ 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

7 records at the apex

Found

Read from
192.174.68.100:53
TypeValueTTL
SOAanycast.regdns1.de. hostmaster.partnergate.com. 2025115968 7200 3600 604800 30086400
NSanycast.regdns1.de.600
NSanycast.regdns2.net.600
A91.99.104.2417200
AAAA2a01:4f8:c0c:84f4::17200
MX100 mail.s2survey.net.7200
TXT"v=spf1 a mx include:s2survey.net include:support.soscisurvey.de -all"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 2h, AAAA 2h, MX 2h, 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