ollydbg.de

Checked 21 October 2026, 23:41 UTC · via 8.8.8.8
!Passed with warnings
19 passed 2 warnings 0 failed 8 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.kundencontroller.de, ns2.kundencontroller.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.kundencontroller.de, ns2.kundencontroller.de
NS in the zone
ns1.kundencontroller.de, ns2.kundencontroller.de
NameserverAddressesNetwork (AS)Glue
ns1.kundencontroller.de85.31.185.126 2a02:180:ffff:1::551f:b97eAS35366 ISPPRO-AS - ISPpro Internet KG, DE AS35366 ISPPRO-AS - ISPpro Internet KG, DE85.31.185.126 2a02:180:ffff:1::551f:b97e
ns2.kundencontroller.de85.31.184.6 2a02:180:ffff:1::551f:b86AS35366 ISPPRO-AS - ISPpro Internet KG, DE AS35366 ISPPRO-AS - ISPpro Internet KG, DE85.31.184.6 2a02:180:ffff:1::551f:b86

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.kundencontroller.de, ns2.kundencontroller.de.
    #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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a02:180:ffff::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS35366 (ISPPRO-AS - ISPpro Internet KG, DE): 4 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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.kundencontroller.de 85.31.185.126NOERROR, 18 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.11
ns1.kundencontroller.de 2a02:180:ffff:1::551f:b97eNOERROR, 19 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.11
ns2.kundencontroller.de 85.31.184.6NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.11
ns2.kundencontroller.de 2a02:180:ffff:1::551f:b86NOERROR, 17 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.11

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.kundencontroller.de: "PowerDNS Authoritative Server 4.1.11"; ns2.kundencontroller.de: "PowerDNS Authoritative Server 4.1.11". 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 0 · primary ns1.kundencontroller.de

Found

Primary (MNAME)
ns1.kundencontroller.de
Contact (RNAME)
hostmaster.kundencontroller.de
Serial
0
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.kundencontroller.de (85.31.185.126)0
ns1.kundencontroller.de (2a02:180:ffff:1::551f:b97e)0
ns2.kundencontroller.de (85.31.184.6)0
ns2.kundencontroller.de (2a02:180:ffff:1::551f:b86)0

Checks

  • ✓ Serial 0 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.kundencontroller.de is one of the listed nameservers.
  • ✓ Contact hostmaster@kundencontroller.de #25
    The SOA RNAME hostmaster.kundencontroller.de means hostmaster@kundencontroller.de.
  • ✓ Counter serial #26
    The serial 0 is a plain counter.

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

6 records at the apex

Found

Read from
85.31.185.126:53
TypeValueTTL
SOAns1.kundencontroller.de. hostmaster.kundencontroller.de. 0 10800 3600 604800 360086400
NSns1.kundencontroller.de.86400
NSns2.kundencontroller.de.86400
A85.31.185.1503600
MX20 mx20.kundencontroller.de.86400
MX10 mx10.kundencontroller.de.86400

Checks

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