weisser-ring.de

Checked 22 October 2026, 01:00 UTC · via 8.8.8.8
!Passed with warnings
21 passed 1 warning 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.telekom.net, pns.dtag.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.telekom.net, pns.dtag.de
NS in the zone
ns1.telekom.net, pns.dtag.de
NameserverAddressesNetwork (AS)Glue
ns1.telekom.net212.185.24.65 2003:180:a:1000::53AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE-
pns.dtag.de194.25.0.125 2003:40:8000::100AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE194.25.0.125 2003:40:8000::100

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.telekom.net, pns.dtag.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 (AS3320 (DTAG - Deutsche Telekom AG, DE): 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
ns1.telekom.net 212.185.24.65NOERROR, 3 ms, authoritativenoyes / yesrefusedDomainNameServer
ns1.telekom.net 2003:180:a:1000::53NOERROR, 3 ms, authoritativenoyes / yesrefusedDomainNameServer
pns.dtag.de 194.25.0.125NOERROR, 9 ms, authoritativenoyes / yesrefusedDomainNameServer
pns.dtag.de 2003:40:8000::100NOERROR, 8 ms, authoritativenoyes / yesrefusedDomainNameServer

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.telekom.net: "DomainNameServer"; pns.dtag.de: "DomainNameServer".
    #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 2026101600 · primary pns.dtag.de

Found

Primary (MNAME)
pns.dtag.de
Contact (RNAME)
dns.telekom.de
Serial
2026101600
Refresh / retry
10800 s / 3600 s
Expire
2419200 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.telekom.net (212.185.24.65)2026101600
ns1.telekom.net (2003:180:a:1000::53)2026101600
pns.dtag.de (194.25.0.125)2026101600
pns.dtag.de (2003:40:8000::100)2026101600

Checks

  • ✓ Serial 2026101600 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 28d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver pns.dtag.de is one of the listed nameservers.
  • ✓ Contact dns@telekom.de #25
    The SOA RNAME dns.telekom.de means dns@telekom.de.
  • ✓ Date-based serial #26
    The serial 2026101600 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

info

8 records at the apex

Found

Read from
212.185.24.65:53
TypeValueTTL
SOApns.dtag.de. dns.telekom.de. 2026101600 10800 3600 2419200 360043200
NSpns.dtag.de.43200
NSns1.telekom.net.43200
A49.13.84.173600
MX10 smtp.weisser-ring.de.172800
TXT"MS=A309BCB45F903F0CB9354C9C7D78A6B6B3B9F4E3"300
TXT"google-site-verification=mMnGYWeHcjyytDmMA4oAn7ZFboQcSwl3WvwQOgioA4E"300
TXT"v=spf1 a mx ip4:93.159.248.236/32 include:spf.nl2go.com include:_spf.odoo.com -all"300

Checks

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