lancom-systems.de

Checked 21 October 2026, 23:11 UTC · via 8.8.8.8
!Passed with warnings
20 passed 3 warnings 0 failed 6 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

pri.mordac.de, sec.mordac.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
pri.mordac.de, sec.mordac.de
NS in the zone
pri.mordac.de, sec.mordac.de
NameserverAddressesNetwork (AS)Glue
pri.mordac.de82.98.82.22AS12306 PLUSLINE - Plus.line AG, DE-
sec.mordac.de185.26.156.10AS58010 UVENSYS - uvensys GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: pri.mordac.de, sec.mordac.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: AS12306 (PLUSLINE - Plus.line AG, DE): 1 address; AS58010 (UVENSYS - uvensys 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
pri.mordac.de 82.98.82.22NOERROR, 4 ms, authoritativenoyes / norefused-
sec.mordac.de 185.26.156.10NOERROR, 5 ms, authoritativenoyes / norefused-

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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: pri.mordac.de (82.98.82.22), sec.mordac.de (185.26.156.10).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 1792621795 · primary pri.mordac.de

Found

Primary (MNAME)
pri.mordac.de
Contact (RNAME)
hostmaster.lancom-systems.de
Serial
1792621795
Refresh / retry
16384 s / 2048 s
Expire
1048576 s
Negative TTL
2560 s

Serial per nameserver

NameserverSerial
pri.mordac.de (82.98.82.22)1792621795
sec.mordac.de (185.26.156.10)1792621795

Checks

  • ✓ Serial 1792621795 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h33m4s, retry 34m8s, expire 291h16m16s, negative TTL 42m40s.
  • ✓ Primary is a public nameserver #24
    The primary nameserver pri.mordac.de is one of the listed nameservers.
  • ✓ Contact hostmaster@lancom-systems.de #25
    The SOA RNAME hostmaster.lancom-systems.de means hostmaster@lancom-systems.de.
  • ✓ Timestamp serial #26
    The serial 1792621795 is a Unix timestamp (2026-10-21 22:29 UTC).

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

9 records at the apex

Found

Read from
82.98.82.22:53
TypeValueTTL
SOApri.mordac.de. hostmaster.lancom-systems.de. 1792621795 16384 2048 1048576 25602560
NSpri.mordac.de.345600
NSsec.mordac.de.345600
A176.9.82.1683600
AAAA2a01:4f8:151:20a3::23600
MX10 mail.lancom.de.3600
TXT"_wu9br89llck18i5efoybe74wulgz3kl"3600
TXT"google-site-verification=fUuN6dYCd3Kbk1ry-3UtpcAayMBj0Qq7zBjhTKDD6Xs"3600
TXT"v=spf1 +a ip4:176.9.12.109 ip4:176.9.82.168 ip4:188.40.147.252 ip4:213.133.111.157 ip4:49.12.235.89 ip6:2a01:04f8:0151:20a3:000" "0:0000:0000:0002 ~all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 1h, MX 1h, NS 4d. The NS TTL at the parent is 1d and in the zone 4d; resolvers may use either.
  • ✓ 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