mintzukunftschaffen.de

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

info

ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com
NS in the zone
ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com
NameserverAddressesNetwork (AS)Glue
ns1.wordpress.com198.181.116.9 2a04:fa87:ffff::c6b5:7409AS2635 AUTOMATTIC - Automattic, Inc, US AS2635 AUTOMATTIC - Automattic, Inc, US-
ns2.wordpress.com198.181.117.9 2a04:fa87:ffff::c6b5:7509AS2635 AUTOMATTIC - Automattic, Inc, US AS2635 AUTOMATTIC - Automattic, Inc, US-
ns3.wordpress.com192.0.74.9 2620:115:c00f::c000:4a09AS2635 AUTOMATTIC - Automattic, Inc, US AS2635 AUTOMATTIC - Automattic, Inc, US-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com.
  • ✓ 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 3 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS2635 (AUTOMATTIC - Automattic, Inc, US): 6 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 .com
    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

info

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.wordpress.com 198.181.116.9NOERROR, 4 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns1.wordpress.com 2a04:fa87:ffff::c6b5:7409NOERROR, 4 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2.wordpress.com 198.181.117.9NOERROR, 3 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2.wordpress.com 2a04:fa87:ffff::c6b5:7509NOERROR, 4 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns3.wordpress.com 192.0.74.9NOERROR, 4 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns3.wordpress.com 2620:115:c00f::c000:4a09NOERROR, 4 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.wordpress.com: "Served by PowerDNS - https://www.powerdns.com/"; ns2.wordpress.com: "Served by PowerDNS - https://www.powerdns.com/"; ns3.wordpress.com: "Served by PowerDNS - https://www.powerdns.com/".
    #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 2005071858 · primary ns1.wordpress.com

Found

Primary (MNAME)
ns1.wordpress.com
Contact (RNAME)
hostmaster.wordpress.com
Serial
2005071858
Refresh / retry
14400 s / 7200 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.wordpress.com (198.181.116.9)2005071858
ns1.wordpress.com (2a04:fa87:ffff::c6b5:7409)2005071858
ns2.wordpress.com (198.181.117.9)2005071858
ns2.wordpress.com (2a04:fa87:ffff::c6b5:7509)2005071858
ns3.wordpress.com (192.0.74.9)2005071858
ns3.wordpress.com (2620:115:c00f::c000:4a09)2005071858

Checks

  • ✓ Serial 2005071858 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 2h, expire 7d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.wordpress.com is one of the listed nameservers.
  • ✓ Contact hostmaster@wordpress.com #25
    The SOA RNAME hostmaster.wordpress.com means hostmaster@wordpress.com.
  • ✓ Date-based serial #26
    The serial 2005071858 follows the YYYYMMDDnn convention (2005-07-18).

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

17 records at the apex

Found

Read from
198.181.116.9:53
TypeValueTTL
SOAns1.wordpress.com. hostmaster.wordpress.com. 2005071858 14400 7200 604800 30086400
NSns2.wordpress.com.86400
NSns3.wordpress.com.86400
NSns1.wordpress.com.86400
A192.0.78.2123600
A192.0.78.1823600
MX30 aspmx4.googlemail.com.14400
MX30 aspmx5.googlemail.com.14400
MX30 aspmx2.googlemail.com.14400
MX10 aspmx.l.google.com.14400
MX20 alt2.aspmx.l.google.com.14400
MX30 aspmx3.googlemail.com.14400
MX0 alt1.aspmx.l.google.com.14400
TXT"google-site-verification=w44aPqgvfVvwgiQEgC6rOthQo8T_g5o4aQMsJm2d8aA"3600
TXT"v=spf1 a mx include:_spf.google.com include:amazonses.com ip4:212.83.50.128 include:_spf.wpcloud.com ~all"3600
TXT"atlassian-domain-verification=2Le9XnUOZJP8mfsWMCtaEzzlBf9vRbtZaR3d4MDskZMNU/SHEh4nKMeR5WJ9rm/7"3600
TXT"atlassian-domain-verification=tExwkbyhCT9XuqHSaOXwG23Szg7VRNMeA1GSPn30OOiWsvfgvYw7axUIQtXktFfF"3600

Checks

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