fernsehserien.de

Checked 21 October 2026, 22:20 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

warn

ns1.plusserver.com, ns2.plusserver.com, ns3.plusserver.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.plusserver.com, ns2.plusserver.com, ns3.plusserver.com
NS in the zone
ns1.plusserver.com, ns2.plusserver.com, ns3.plusserver.com
NameserverAddressesNetwork (AS)Glue
ns1.plusserver.com85.25.65.9 2a02:cbf7:100:10:0:53:1:1AS61157 PLUSSERVER-ASN1 - PlusServer GmbH, DE AS61157 PLUSSERVER-ASN1 - PlusServer GmbH, DE-
ns2.plusserver.com85.25.65.10 2a02:cbf7:100:10:0:53:1:2AS61157 PLUSSERVER-ASN1 - PlusServer GmbH, DE AS61157 PLUSSERVER-ASN1 - PlusServer GmbH, DE-
ns3.plusserver.com85.25.65.14 2a02:cbf7:100:10:0:53:1:3AS61157 PLUSSERVER-ASN1 - PlusServer GmbH, DE AS61157 PLUSSERVER-ASN1 - PlusServer GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.plusserver.com, ns2.plusserver.com, ns3.plusserver.com.
  • ✓ 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 one network
    all IPv4 addresses are in 85.25.65.0/24; all IPv6 addresses are in 2a02:cbf7:100::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS61157 (PLUSSERVER-ASN1 - PlusServer GmbH, DE): 6 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.plusserver.com 85.25.65.9NOERROR, 7 ms, authoritativenoyes / yesrefused-
ns1.plusserver.com 2a02:cbf7:100:10:0:53:1:1NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns2.plusserver.com 85.25.65.10NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns2.plusserver.com 2a02:cbf7:100:10:0:53:1:2NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns3.plusserver.com 85.25.65.14NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns3.plusserver.com 2a02:cbf7:100:10:0:53:1:3NOERROR, 14 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2026083101 · primary ns1.plusserver.com

Found

Primary (MNAME)
ns1.plusserver.com
Contact (RNAME)
hostmaster.plusserver.com
Serial
2026083101
Refresh / retry
1800 s / 900 s
Expire
604800 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.plusserver.com (85.25.65.9)2026083101
ns1.plusserver.com (2a02:cbf7:100:10:0:53:1:1)2026083101
ns2.plusserver.com (85.25.65.10)2026083101
ns2.plusserver.com (2a02:cbf7:100:10:0:53:1:2)2026083101
ns3.plusserver.com (85.25.65.14)2026083101
ns3.plusserver.com (2a02:cbf7:100:10:0:53:1:3)2026083101

Checks

  • ✓ Serial 2026083101 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 30m, retry 15m, expire 7d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.plusserver.com is one of the listed nameservers.
  • ✓ Contact hostmaster@plusserver.com #25
    The SOA RNAME hostmaster.plusserver.com means hostmaster@plusserver.com.
  • ✓ Date-based serial #26
    The serial 2026083101 follows the YYYYMMDDnn convention (2026-08-31).

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

9 records at the apex

Found

Read from
85.25.65.9:53
TypeValueTTL
SOAns1.plusserver.com. hostmaster.plusserver.com. 2026083101 1800 900 604800 90086400
NSns1.plusserver.com.3600
NSns3.plusserver.com.3600
NSns2.plusserver.com.3600
A85.10.215.18086400
MX20 mxext3.mailbox.org.86400
MX10 mxext2.mailbox.org.86400
MX10 mxext1.mailbox.org.86400
TXT"v=spf1 ip4:62.138.249.138 ip4:62.138.249.139 ip4:62.138.249.140 ip4:62.138.249.141 ip4:62.138.249.142 ip4:62.138.249.143 a:dedi396.your-server.de a:dedi580.your-server.de include:amazonses.com include:mailbox.org -all"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, MX 1d, 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.
  • 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