rotary.de

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

info

ns1.mcs.de, ns2.mcs.de, ns3.mcs.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.mcs.de, ns2.mcs.de, ns3.mcs.de
NS in the zone
ns1.mcs.de, ns2.mcs.de, ns3.mcs.de
NameserverAddressesNetwork (AS)Glue
ns1.mcs.de147.78.89.212 2a09:2040:0:16::10AS215992 MCS-AS - MCS GmbH, DE AS215992 MCS-AS - MCS GmbH, DE147.78.89.212 2a09:2040:0:16::10
ns2.mcs.de147.78.89.220 2a09:2040:0:17::10AS215992 MCS-AS - MCS GmbH, DE AS215992 MCS-AS - MCS GmbH, DE147.78.89.220 2a09:2040:0:17::10
ns3.mcs.de194.13.83.222 2a03:4000:43:502::1AS197540 netcup-AS - netcup GmbH, DE AS197540 netcup-AS - netcup GmbH, DE194.13.83.222 2a03:4000:43:502::1

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.mcs.de, ns2.mcs.de, ns3.mcs.de.
  • ✓ 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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS197540 (netcup-AS - netcup GmbH, DE): 2 addresses; AS215992 (MCS-AS - MCS GmbH, DE): 4 addresses.
  • 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

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.mcs.de 147.78.89.212NOERROR, 12 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns1.mcs.de 2a09:2040:0:16::10NOERROR, 12 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns2.mcs.de 147.78.89.220NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns2.mcs.de 2a09:2040:0:17::10NOERROR, 14 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns3.mcs.de 194.13.83.222NOERROR, 1 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns3.mcs.de 2a03:4000:43:502::1NOERROR, 1 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3

Checks

  • ✓ All respond #14
    All 6 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.mcs.de: "PowerDNS Authoritative Server 4.8.3"; ns2.mcs.de: "PowerDNS Authoritative Server 4.8.3"; ns3.mcs.de: "PowerDNS Authoritative Server 4.8.3". 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 2026091702 · primary ns1.mcs.de

Found

Primary (MNAME)
ns1.mcs.de
Contact (RNAME)
hostmaster.mcs.de
Serial
2026091702
Refresh / retry
14400 s / 3600 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.mcs.de (147.78.89.212)2026091702
ns1.mcs.de (2a09:2040:0:16::10)2026091702
ns2.mcs.de (147.78.89.220)2026091702
ns2.mcs.de (2a09:2040:0:17::10)2026091702
ns3.mcs.de (194.13.83.222)2026091702
ns3.mcs.de (2a03:4000:43:502::1)2026091702

Checks

  • ✓ Serial 2026091702 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 1h, expire 7d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.mcs.de is one of the listed nameservers.
  • ✓ Contact hostmaster@mcs.de #25
    The SOA RNAME hostmaster.mcs.de means hostmaster@mcs.de.
  • ✓ Date-based serial #26
    The serial 2026091702 follows the YYYYMMDDnn convention (2026-09-17).

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

21 records at the apex

Found

Read from
147.78.89.212:53
TypeValueTTL
SOAns1.mcs.de. hostmaster.mcs.de. 2026091702 14400 3600 604800 6003600
NSns2.mcs.de.3600
NSns1.mcs.de.3600
NSns3.mcs.de.3600
A185.215.158.100300
MX10 mymail.rotary.de.3600
TXT"v=spf1 a mx ip4:91.26.205.90 ip4:195.244.113.61 a:mail.rotary-bna.de ip4:89.21.51.82 ip4:80.153.226.126 ip4:91.26.205.91 include:1._spf.plusserver.com include:spf.crsend.com include:agenturserver.de ~all"3600
TXT"MS=ms93286259"3600
TXT"domainVerification=199698b8-c01f-4b28-8394-61dbce81363f"3600
TXT"_globalsign-domain-verification=7laxTBIuQRayLVXPrl9yMcy_xRf4eo3O2PBLbJq2Xa"3600
TXT"_globalsign-domain-verification=PCxwzkwdIIvdtyEOI4FczPHTxnxdtUnVQGZda23ITE"3600
TXT"google-site-verification=DmH_xT5Yuzfyy100qEETPrJbrAhdg7z8acEA0mY_Isc"3600
TXT"google-site-verification=U8x05AUyn7K5b5mEWEnG-vMp4vm7Gqk1LaMrDxX6ocg"3600
TXT"google-site-verification=gbBSLF4XEYfUtSAGZFNaqENsJ2mGOaxfxhx2ZfvU3n4"3600
CAA0 issue "sectigo.com"3600
CAA0 issue "certum.pl"3600
CAA0 issuewild "certum.eu"3600
CAA0 issuewild "sectigo.com"3600
CAA0 issuewild "certum.pl"3600
CAA0 issue "certum.eu"3600
CAA0 issue "letsencrypt.org"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.
  • 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: sectigo.com, certum.pl, certum.eu, letsencrypt.org.