homepage-baukasten.de

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

warn

ns01.webme.com, ns02.webme.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns01.webme.com, ns02.webme.com
NS in the zone
ns01.webme.com, ns02.webme.com
NameserverAddressesNetwork (AS)Glue
ns01.webme.com217.160.80.161AS8560 IONOS-AS - IONOS SE, DE-
ns02.webme.com217.160.81.161AS8560 IONOS-AS - IONOS SE, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns01.webme.com, ns02.webme.com.
    #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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8560 (IONOS-AS - IONOS SE, DE): 2 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns01.webme.com 217.160.80.161NOERROR, 9 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns02.webme.com 217.160.81.161NOERROR, 10 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/

Checks

  • ✓ All respond #14
    All 2 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: ns01.webme.com: "Served by PowerDNS - https://www.powerdns.com/"; ns02.webme.com: "Served by PowerDNS - https://www.powerdns.com/".
    #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 2025121803 · primary ns01.webme.com

Found

Primary (MNAME)
ns01.webme.com
Contact (RNAME)
dnsadmin.webme.com
Serial
2025121803
Refresh / retry
43200 s / 7200 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns01.webme.com (217.160.80.161)2025121803
ns02.webme.com (217.160.81.161)2025121803

Checks

  • ✓ Serial 2025121803 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 2h, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.webme.com is one of the listed nameservers.
  • ✓ Contact dnsadmin@webme.com #25
    The SOA RNAME dnsadmin.webme.com means dnsadmin@webme.com.
  • ✓ Date-based serial #26
    The serial 2025121803 follows the YYYYMMDDnn convention (2025-12-18).

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
217.160.80.161:53
TypeValueTTL
SOAns01.webme.com. dnsadmin.webme.com. 2025121803 43200 7200 1209600 8640086400
NSns02.webme.com.86400
NSns01.webme.com.86400
A193.238.27.2186400
MX10 mx1.webme-tech.net.86400
TXT"v=spf1 a mx a:mail.homepage-baukasten-mail.de a:mx1.webme-tech.net ip4:88.198.64.18 ip4:80.190.202.0/25 ip4:193.238.27.0/24 ~all"60
TXT"google-site-verification=vamLF_XzLOGBE0A-JH7XP_iruz_Q9nz4Fh1in-NpNi8"60
TXT"201706301130030gvnafz0kz562qfpsrk0b2dti9i1keigtwkmh4w5u5totqk137"60

Checks

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