pfalz-express.de

Checked 21 October 2026, 23:50 UTC · via 8.8.8.8
!Passed with warnings
22 passed 1 warning 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.webhosting-franken.de, ns2.webhosting-franken.de, sns.webhosting-franken.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.webhosting-franken.de, ns2.webhosting-franken.de, sns.webhosting-franken.de
NS in the zone
ns1.webhosting-franken.de, ns2.webhosting-franken.de, sns.webhosting-franken.de
NameserverAddressesNetwork (AS)Glue
ns1.webhosting-franken.de116.203.210.55 2a01:4f8:1c1e:4fb9::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE116.203.210.55 2a01:4f8:1c1e:4fb9::1
ns2.webhosting-franken.de65.108.94.63 2a01:4f9:c012:ce39::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE65.108.94.63 2a01:4f9:c012:ce39::1
sns.webhosting-franken.de159.69.49.212 2a01:4f8:c012:daad::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE159.69.49.212 2a01:4f8:c012:daad::1

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.webhosting-franken.de, ns2.webhosting-franken.de, sns.webhosting-franken.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 3 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online 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 .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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.webhosting-franken.de 116.203.210.55NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns1.webhosting-franken.de 2a01:4f8:1c1e:4fb9::1NOERROR, 2 ms, authoritativenoyes / yesrefused-
ns2.webhosting-franken.de 65.108.94.63NOERROR, 24 ms, authoritativenoyes / yesrefused-
ns2.webhosting-franken.de 2a01:4f9:c012:ce39::1NOERROR, 25 ms, authoritativenoyes / yesrefused-
sns.webhosting-franken.de 159.69.49.212NOERROR, 9 ms, authoritativenoyes / yesrefused-
sns.webhosting-franken.de 2a01:4f8:c012:daad::1NOERROR, 9 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 2012011101 · primary ns1.webhosting-franken.de

Found

Primary (MNAME)
ns1.webhosting-franken.de
Contact (RNAME)
postmaster.webhosting-franken.de
Serial
2012011101
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.webhosting-franken.de (116.203.210.55)2012011101
ns1.webhosting-franken.de (2a01:4f8:1c1e:4fb9::1)2012011101
ns2.webhosting-franken.de (65.108.94.63)2012011101
ns2.webhosting-franken.de (2a01:4f9:c012:ce39::1)2012011101
sns.webhosting-franken.de (159.69.49.212)2012011101
sns.webhosting-franken.de (2a01:4f8:c012:daad::1)2012011101

Checks

  • ✓ Serial 2012011101 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.webhosting-franken.de is one of the listed nameservers.
  • ✓ Contact postmaster@webhosting-franken.de #25
    The SOA RNAME postmaster.webhosting-franken.de means postmaster@webhosting-franken.de.
  • ✓ Date-based serial #26
    The serial 2012011101 follows the YYYYMMDDnn convention (2012-01-11).

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

7 records at the apex

Found

Read from
116.203.210.55:53
TypeValueTTL
SOAns1.webhosting-franken.de. postmaster.webhosting-franken.de. 2012011101 28800 7200 604800 36003600
NSsns.webhosting-franken.de.3600
NSns2.webhosting-franken.de.3600
NSns1.webhosting-franken.de.3600
A162.55.71.1943600
MX10 mail.pfalz-express.de.3600
TXT"v=spf1 mx a ~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.
  • 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