teegschwendner.de

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

ns01.intersolute.de, ns02.intersolute.de, ns03.intersolute.eu, ns04.intersolute.eu

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns01.intersolute.de, ns02.intersolute.de, ns03.intersolute.eu, ns04.intersolute.eu
NS in the zone
ns01.intersolute.de, ns02.intersolute.de, ns03.intersolute.eu, ns04.intersolute.eu
NameserverAddressesNetwork (AS)Glue
ns01.intersolute.de91.215.75.14AS49609 INTERSOLUTE - Intersolute GmbH, DE91.215.75.14
ns02.intersolute.de80.82.216.230AS24961 MYLOC-AS - WIIT AG, DE80.82.216.230
ns03.intersolute.eu51.195.47.8AS16276 OVH - OVH SAS, FR-
ns04.intersolute.eu51.178.44.64AS16276 OVH - OVH SAS, FR-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns01.intersolute.de, ns02.intersolute.de, ns03.intersolute.eu, ns04.intersolute.eu.
  • ✓ 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 4 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 2 addresses; AS24961 (MYLOC-AS - WIIT AG, DE): 1 address; AS49609 (INTERSOLUTE - Intersolute GmbH, DE): 1 address.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .eu.
  • !
    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
ns01.intersolute.de 91.215.75.14NOERROR, 8 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.0.3
ns02.intersolute.de 80.82.216.230NOERROR, 7 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.0.3
ns03.intersolute.eu 51.195.47.8NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1
ns04.intersolute.eu 51.178.44.64NOERROR, 7 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1

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: ns01.intersolute.de: "PowerDNS Authoritative Server 4.0.3"; ns02.intersolute.de: "PowerDNS Authoritative Server 4.0.3"; ns03.intersolute.eu: "PowerDNS Authoritative Server 4.4.1"; ns04.intersolute.eu: "PowerDNS Authoritative Server 4.4.1". 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 2026102201 · primary ns01.intersolute.de

Found

Primary (MNAME)
ns01.intersolute.de
Contact (RNAME)
ticket.intersolute.de
Serial
2026102201
Refresh / retry
86400 s / 10800 s
Expire
3600000 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns01.intersolute.de (91.215.75.14)2026102201
ns02.intersolute.de (80.82.216.230)2026102201
ns03.intersolute.eu (51.195.47.8)2026102201
ns04.intersolute.eu (51.178.44.64)2026102201

Checks

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

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

warn

14 records at the apex

Found

Read from
91.215.75.14:53
TypeValueTTL
SOAns01.intersolute.de. ticket.intersolute.de. 2026102201 86400 10800 3600000 8640086400
NSns02.intersolute.de.86400
NSns03.intersolute.eu.86400
NSns04.intersolute.eu.86400
NSns01.intersolute.de.86400
A80.90.17.121300
MX20 mx2.intersolute.de.60
MX10 mc.intersolute.de.60
TXT"google-site-verification=Xn0pulfznDkPiowu4I_BFZtfrzftgnEHtkCbQRR2MM8"3600
TXT"MS=3A311C379735A83DC3EDFF9560A82F6C814652E5"3600
TXT"v=spf1 mx ip4:80.82.213.24 ip4:80.82.213.175 ip4:91.215.72.141 ip4:91.215.72.142 ip4:91.215.74.101 ip4:91.215.74.102 ip4:91.215.72.90 ip4:91.215.75.5 ip4:91.215.72.136/29 -all"3600
TXT"brevo-code:d6f275d185177284747105ec5f10fac1"3600
TXT"_uxsactx151j6bnuq20vq9ckpl0qbpwv"3600
TXT"google-site-verification=tS7OhVC1CEPs9-XDei2dFEwPogIsBy6j-jl3Eucz0jw"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). Low TTLs are useful just before a planned change.
    #32
  • ✓ 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