jimdo.de

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

ns01.jimdo-server.com, ns02.jimdo-server.com, ns03.jimdo-server.com, ns04.jimdo-server.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns01.jimdo-server.com, ns02.jimdo-server.com, ns03.jimdo-server.com, ns04.jimdo-server.com
NS in the zone
ns01.jimdo-server.com, ns02.jimdo-server.com, ns03.jimdo-server.com, ns04.jimdo-server.com
NameserverAddressesNetwork (AS)Glue
ns01.jimdo-server.com62.116.159.4 2001:4178:3:a357:62:116:159:4AS15456 INTERNETX-AS - InterNetX GmbH, DE AS15456 INTERNETX-AS - InterNetX GmbH, DE-
ns02.jimdo-server.com217.160.113.37 2001:8d8:580:401:217:160:113:37AS8560 IONOS-AS - IONOS SE, DE AS8560 IONOS-AS - IONOS SE, DE-
ns03.jimdo-server.com89.146.248.4 2a01:130:2000:118:89:146:248:4AS8495 INTERNET_AG - INTERNET AG Global Network, DE AS8495 INTERNET_AG - INTERNET AG Global Network, DE-
ns04.jimdo-server.com74.208.254.4 2607:f1c0:1800:8091:74:208:254:4AS8560 IONOS-AS - IONOS SE, DE AS8560 IONOS-AS - IONOS SE, DE-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns01.jimdo-server.com, ns02.jimdo-server.com, ns03.jimdo-server.com, ns04.jimdo-server.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 4 IPv4 /24s and 4 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS15456 (INTERNETX-AS - InterNetX GmbH, DE): 2 addresses; AS8495 (INTERNET_AG - INTERNET AG Global Network, DE): 2 addresses; AS8560 (IONOS-AS - IONOS SE, DE): 4 addresses.
  • 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

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns01.jimdo-server.com 62.116.159.4NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns01.jimdo-server.com 2001:4178:3:a357:62:116:159:4NOERROR, 19 ms, authoritativenoyes / yesrefused-
ns02.jimdo-server.com 217.160.113.37NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns02.jimdo-server.com 2001:8d8:580:401:217:160:113:37NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns03.jimdo-server.com 89.146.248.4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns03.jimdo-server.com 2a01:130:2000:118:89:146:248:4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns04.jimdo-server.com 74.208.254.4NOERROR, 117 ms, authoritativenoyes / yesrefused-
ns04.jimdo-server.com 2607:f1c0:1800:8091:74:208:254:4NOERROR, 117 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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

pass

serial 2026102100 · primary ns01.jimdo-server.com

Found

Primary (MNAME)
ns01.jimdo-server.com
Contact (RNAME)
server-admin.northclick.de
Serial
2026102100
Refresh / retry
43200 s / 7200 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns01.jimdo-server.com (62.116.159.4)2026102100
ns01.jimdo-server.com (2001:4178:3:a357:62:116:159:4)2026102100
ns02.jimdo-server.com (217.160.113.37)2026102100
ns02.jimdo-server.com (2001:8d8:580:401:217:160:113:37)2026102100
ns03.jimdo-server.com (89.146.248.4)2026102100
ns03.jimdo-server.com (2a01:130:2000:118:89:146:248:4)2026102100
ns04.jimdo-server.com (74.208.254.4)2026102100
ns04.jimdo-server.com (2607:f1c0:1800:8091:74:208:254:4)2026102100

Checks

  • ✓ Serial 2026102100 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 2h, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.jimdo-server.com is one of the listed nameservers.
  • ✓ Contact server-admin@northclick.de #25
    The SOA RNAME server-admin.northclick.de means server-admin@northclick.de.
  • ✓ Date-based serial #26
    The serial 2026102100 follows the YYYYMMDDnn convention (2026-10-21).

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

16 records at the apex

Found

Read from
62.116.159.4:53
TypeValueTTL
SOAns01.jimdo-server.com. server-admin.northclick.de. 2026102100 43200 7200 1209600 8640086400
NSns04.jimdo-server.com.86400
NSns03.jimdo-server.com.86400
NSns01.jimdo-server.com.86400
NSns02.jimdo-server.com.86400
A172.64.148.903600
A104.18.39.1663600
MX30 aspmx3.googlemail.com.3600
MX20 alt1.aspmx.l.google.com.3600
MX10 aspmx.l.google.com.3600
MX20 alt2.aspmx.l.google.com.3600
MX30 aspmx2.googlemail.com.3600
TXT"google-site-verification=-Ef0-MCtZ4ClStCMA7QRCZImM0dd11BYM1G70m6mRGI"3600
TXT"_globalsign-domain-verification=7JmN6dazOT7LXjyHvi_YmaRlN4ZcwfGCyQ7CfElelu"3600
TXT"_globalsign-domain-verification=1yXH4s6C8kR7yRNKNZJe8Q95_7vd6x9VOsBtaXUzX_"3600
TXT"v=spf1 include:servers.mcsv.net include:_spf.google.com include:mail.zendesk.com include:sendgrid.net include:spf.mandrillapp.com ~all"3600

Checks

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