ctm-festival.de

Checked 21 October 2026, 22:11 UTC · via 8.8.8.8
!Passed with warnings
20 passed 1 warning 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

ens1.sinma.de, ens2.sinma.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ens1.sinma.de, ens2.sinma.de
NS in the zone
ens1.sinma.de, ens2.sinma.de
NameserverAddressesNetwork (AS)Glue
ens1.sinma.de83.223.90.206 2a01:30:0:13:5054:ffaa:fbb4:a9dcAS8875 SINMA-ASN - sinma GmbH, DE AS8875 SINMA-ASN - sinma GmbH, DE-
ens2.sinma.de83.223.84.15 2a01:30:d000:3::12AS8875 SINMA-ASN - sinma GmbH, DE AS8875 SINMA-ASN - sinma GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ens1.sinma.de, ens2.sinma.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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8875 (SINMA-ASN - sinma GmbH, 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

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ens1.sinma.de 83.223.90.206NOERROR, 9 ms, authoritativenoyes / yesrefused-
ens1.sinma.de 2a01:30:0:13:5054:ffaa:fbb4:a9dcNOERROR, 13 ms, authoritativenoyes / yesrefused-
ens2.sinma.de 83.223.84.15NOERROR, 11 ms, authoritativenoyes / yesrefused-
ens2.sinma.de 2a01:30:d000:3::12NOERROR, 18 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

info

serial 2026070407 · primary dns.einsnull.com

Found

Primary (MNAME)
dns.einsnull.com
Contact (RNAME)
root.dns.einsnull.com
Serial
2026070407
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ens1.sinma.de (83.223.90.206)2026070407
ens1.sinma.de (2a01:30:0:13:5054:ffaa:fbb4:a9dc)2026070407
ens2.sinma.de (83.223.84.15)2026070407
ens2.sinma.de (2a01:30:d000:3::12)2026070407

Checks

  • ✓ Serial 2026070407 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 14d, negative TTL 1d.
  • i
    Hidden master
    The primary nameserver dns.einsnull.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact root@dns.einsnull.com #25
    The SOA RNAME root.dns.einsnull.com means root@dns.einsnull.com.
  • ✓ Date-based serial #26
    The serial 2026070407 follows the YYYYMMDDnn convention (2026-07-04).

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

11 records at the apex

Found

Read from
83.223.90.206:53
TypeValueTTL
SOAdns.einsnull.com. root.dns.einsnull.com. 2026070407 10800 3600 1209600 864003600
NSens2.sinma.de.3600
NSens1.sinma.de.3600
A83.223.85.2193600
AAAA2a01:30:0:505:20b6:77ff:fe57:7f73600
MX10 mailserver.sinma.de.3600
MX100 post.sinma.de.3600
TXT"google-site-verification=dHWiEW7PxuHtuiai0U8wBRVM7u86ApIl2-qyqXeVjGY"3600
TXT"v=spf1 include:_spf.sinma.de include:ispgateway.de a:smtp2.shopify.com include:_spf.google.com ~all"3600
TXT"google-gws-recovery-domain-verification=71852433"3600
TXT"google-site-verification=JgL64B5CV9Ke02oH7DcrRl55WuuC7I6wAy9iDi8PnPs"3600

Checks

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