multimania.de

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

ns1.conversis.de, ns2.conversis.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.conversis.de, ns2.conversis.de
NS in the zone
ns1.conversis.de, ns2.conversis.de
NameserverAddressesNetwork (AS)Glue
ns1.conversis.de213.203.208.212AS61157 PLUSSERVER-ASN1 - PlusServer GmbH, DE-
ns2.conversis.de81.7.10.51AS35366 ISPPRO-AS - ISPpro Internet KG, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.conversis.de, ns2.conversis.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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS35366 (ISPPRO-AS - ISPpro Internet KG, DE): 1 address; AS61157 (PLUSSERVER-ASN1 - PlusServer 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

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.conversis.de 213.203.208.212NOERROR, 13 ms, authoritativenoyes / yesrefusedKnot DNS 3.6.0
ns2.conversis.de 81.7.10.51NOERROR, 11 ms, authoritativenoyes / yesrefusedKnot DNS 3.6.0

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.conversis.de: "Knot DNS 3.6.0"; ns2.conversis.de: "Knot DNS 3.6.0". 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 2012052403 · primary ns1.conversis.de

Found

Primary (MNAME)
ns1.conversis.de
Contact (RNAME)
hostmaster.conversis.de
Serial
2012052403
Refresh / retry
86400 s / 7200 s
Expire
3024000 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.conversis.de (213.203.208.212)2012052403
ns2.conversis.de (81.7.10.51)2012052403

Checks

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

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC
Signatures valid until
3 November 2026

DNSKEY in the zone

Key tagRoleAlgorithm
35857ZSK (256)ECDSAP256SHA256 (13)
8540KSK (257)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-03 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-03 07:21 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

4 records at the apex

Found

Read from
213.203.208.212:53
TypeValueTTL
SOAns1.conversis.de. hostmaster.conversis.de. 2012052403 86400 7200 3024000 36003600
NSns1.conversis.de.86400
NSns2.conversis.de.86400
A213.131.252.2543600

Checks

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