muenchenticket.de

Checked 21 October 2026, 23:30 UTC · via 8.8.8.8
!Passed with warnings
20 passed 4 warnings 0 failed 5 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.webport.de, ns2.webport.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.webport.de, ns2.webport.de
NS in the zone
ns1.webport.de, ns2.webport.de, ns3.webportdc.com, ns4.webportdc.com
NameserverAddressesNetwork (AS)Glue
ns1.webport.de88.217.208.5AS8767 MNET-AS - M-net Telekommunikations GmbH, DE88.217.208.5
ns2.webport.de162.55.167.177AS24940 HETZNER-AS - Hetzner Online GmbH, DE162.55.167.177
ns3.webportdc.com (zone only)37.59.108.44AS16276 OVH - OVH SAS, FR-
ns4.webportdc.com (zone only)157.180.112.152AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.webport.de, ns2.webport.de.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns3.webportdc.com, ns4.webportdc.com. ns1.webport.de, ns2.webport.de, ns3.webportdc.com, ns4.webportdc.com report NS ns1.webport.de ns2.webport.de ns3.webportdc.com ns4.webportdc.com.
    #7
  • ✓ 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 4 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 1 address; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS8767 (MNET-AS - M-net Telekommunikations 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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.webport.de 88.217.208.5NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)
ns2.webport.de 162.55.167.177NOERROR, 3 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)
ns3.webportdc.com 37.59.108.44NOERROR, 17 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)
ns4.webportdc.com 157.180.112.152NOERROR, 26 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.webport.de: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)"; ns2.webport.de: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)"; ns3.webportdc.com: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)"; ns4.webportdc.com: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)". Hide or replace the version string.
    #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 2025062302 · primary ns1.webport.de

Found

Primary (MNAME)
ns1.webport.de
Contact (RNAME)
hostmaster.webport.de
Serial
2025062302
Refresh / retry
28800 s / 7200 s
Expire
1814400 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.webport.de (88.217.208.5)2025062302
ns2.webport.de (162.55.167.177)2025062302
ns3.webportdc.com (37.59.108.44)2025062302
ns4.webportdc.com (157.180.112.152)2025062302

Checks

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

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

18 records at the apex

Found

Read from
88.217.208.5:53
TypeValueTTL
SOAns1.webport.de. hostmaster.webport.de. 2025062302 28800 7200 1814400 36003600
NSns1.webport.de.3600
NSns3.webportdc.com.60
NSns2.webport.de.3600
NSns4.webportdc.com.60
A5.75.215.185300
MX20 mx02.hornetsecurity.com.3600
MX30 mx03.hornetsecurity.com.3600
MX40 mx04.hornetsecurity.com.3600
MX10 mx01.hornetsecurity.com.3600
TXT"MS=ms78269145"3600
TXT"google-site-verification=xXx44iTAhlR-TT4BUjlWcAV0y26WxNaZL_2ulPyR5Jo"3600
TXT"t541ktre255yt6652yh655hy1465y561h53u"3600
TXT"google-site-verification=bK7GpdoY2K5ezANh_Xf_EHwU9ATC82EN4IuE0YleaVA"3600
TXT"apple-domain-verification=7SZlJjcYpkyinAGm"3600
TXT"v=spf1 ip4:94.16.7.139 include:_spf.senders.scnem.com include:amazonses.com include:spf.mailjet.com include:spf.protection.outlook.de include:spf.hornetsecurity.com -all"3600
TXT"4mL2B+q3hyIkQJJX1lJFLrhpSU50D1Ioz0MXHietNHYIjUURqQMVoiR3lozeJjMANdkGBhWGHLqAijZbiMPSsA=="3600
TXT"MS=ms86802300"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, 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