playmobil-funpark.de

Checked 21 October 2026, 23:50 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 warnings 0 failed 4 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

ns.bisping.de, ns2.bisping.de, ns3.bisping.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.bisping.de, ns2.bisping.de, ns3.bisping.de
NS in the zone
ns.bisping.de, ns2.bisping.de, ns3.bisping.de
NameserverAddressesNetwork (AS)Glue
ns.bisping.de62.91.2.20AS20686 BISPING - BISPING, DE62.91.2.20
ns2.bisping.de62.91.92.20AS20686 BISPING - BISPING, DE62.91.92.20
ns3.bisping.de91.99.178.218AS24940 HETZNER-AS - Hetzner Online GmbH, DE91.99.178.218

Checks

  • ✓ 3 nameservers #6
    Delegated to ns.bisping.de, ns2.bisping.de, ns3.bisping.de.
  • ✓ 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 3 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20686 (BISPING - BISPING, DE): 2 addresses; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 1 address.
  • i
    All nameserver names under .de
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.bisping.de 62.91.2.20NOERROR, 6 ms, authoritativenoyes / yesrefused-
ns2.bisping.de 62.91.92.20NOERROR, 0 ms, authoritativenoyes / yesrefused-
ns3.bisping.de 91.99.178.218NOERROR, 9 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 3 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 2025121503 · primary ns.bisping.de

Found

Primary (MNAME)
ns.bisping.de
Contact (RNAME)
hostmaster.bisping.de
Serial
2025121503
Refresh / retry
86400 s / 3600 s
Expire
3600000 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns.bisping.de (62.91.2.20)2025121503
ns2.bisping.de (62.91.92.20)2025121503
ns3.bisping.de (91.99.178.218)2025121503

Checks

  • ✓ Serial 2025121503 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 1h, expire 1000h, negative TTL 3h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.bisping.de is one of the listed nameservers.
  • ✓ Contact hostmaster@bisping.de #25
    The SOA RNAME hostmaster.bisping.de means hostmaster@bisping.de.
  • ✓ Date-based serial #26
    The serial 2025121503 follows the YYYYMMDDnn convention (2025-12-15).

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

11 records at the apex

Found

Read from
62.91.2.20:53
TypeValueTTL
SOAns.bisping.de. hostmaster.bisping.de. 2025121503 86400 3600 3600000 108003600
NSns3.bisping.de.3600
NSns2.bisping.de.3600
NSns.bisping.de.3600
A62.91.41.2113600
MX10 mxb-006eac01.gslb.pphosted.com.3600
MX10 mxa-006eac01.gslb.pphosted.com.3600
TXT"MS=ms20633686"1800
TXT"MS=ms61294247"1800
TXT"v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com -all"1800
TXT"2uO0Gl1Xd2EhHTpOwPVAPZlgQ/NhmySju9qYGd6JIK83Mo2BGP06B8s/scNZq7z/c0FkauFv2cSYa21yQMYBcw=="1800

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