opodo.de

Checked 21 October 2026, 23:41 UTC · via 8.8.8.8
!Passed with warnings
19 passed 3 warnings 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.opodo.com, ns2.opodo.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.opodo.com, ns2.opodo.com
NS in the zone
ns1.opodo.com, ns2.opodo.com
NameserverAddressesNetwork (AS)Glue
ns1.opodo.com162.159.0.243 2400:cb00:2049:1::a29f:f3AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
ns2.opodo.com162.159.1.226 2400:cb00:2049:1::a29f:1e2AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.opodo.com, ns2.opodo.com.
    #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.
  • i
    One address family in one network
    all IPv6 addresses are in 2400:cb00:2049::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 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 .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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.opodo.com 162.159.0.243NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
ns1.opodo.com 2400:cb00:2049:1::a29f:f3NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
ns2.opodo.com 162.159.1.226NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
ns2.opodo.com 2400:cb00:2049:1::a29f:1e2NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.opodo.com: "2026.10.2"; ns2.opodo.com: "2026.10.2". 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 2417614111 · primary ns1.opodo.com

Found

Primary (MNAME)
ns1.opodo.com
Contact (RNAME)
dns.cloudflare.com
Serial
2417614111
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
ns1.opodo.com (162.159.0.243)2417614111
ns1.opodo.com (2400:cb00:2049:1::a29f:f3)2417614111
ns2.opodo.com (162.159.1.226)2417614111
ns2.opodo.com (2400:cb00:2049:1::a29f:1e2)2417614111

Checks

  • ✓ Serial 2417614111 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.opodo.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2417614111 is a Unix timestamp (2046-08-11 15:28 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

warn

14 records at the apex

Found

Read from
162.159.0.243:53
TypeValueTTL
SOAns1.opodo.com. dns.cloudflare.com. 2417614111 10000 2400 604800 18001800
NSns1.opodo.com.86400
NSns2.opodo.com.86400
A34.141.6.21260
MX1 aspmx.l.google.com.3600
MX10 alt3.aspmx.l.google.com.3600
MX10 alt4.aspmx.l.google.com.3600
MX5 alt1.aspmx.l.google.com.3600
MX5 alt2.aspmx.l.google.com.3600
TXT"facebook-domain-verification=7k7k6nalghf8pj6yquaspov8g2rmb8"600
TXT"google-site-verification=6adymuYGE8tuULVdrlbDRSvdJ2piTzMdJTk66S5PSik"600
TXT"google-site-verification=GMdzClRpePeleg9w93q2X-3KUF_VZvfTYW0cpCG384U"600
TXT"google-site-verification=uJaXwsl8ay-ijoatxZR8ZrIIcO-5kUJEHTGX2oYktg8"600
TXT"v=spf1 include:spf-a.odigeo.com include:spf-b.odigeo.com include:_spf1.opodo.de include:_spf2.opodo.de include:u1941612.wl.sendgrid.net mx include:spf-b.odigeo.com include:spf-partners.opodo.com ip4:82.197.83.77 ~all"600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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