opodo.fr

Checked 22 October 2026, 04:39 UTC · via 8.8.8.8
✗Problems found
19 passed 3 warnings 1 failed 8 info

Registration

fail

.fr country-code · CSC CORPORATE DOMAINS INC. · expires 2026-10-30

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
CSC CORPORATE DOMAINS INC.
Registered
7 October 2001
Last changed
31 October 2025
Expires
30 October 2026
Status
active
Registry nameservers
ns1.opodo.com, ns2.opodo.com
RDAP server
https://rdap.nic.fr/

Checks

  • i
    .fr 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
    .fr is delegated in the root zone and DNSSEC-signed.
  • ✗
    Expires in 8 days
    The registration expires on 2026-10-30. Renew it now or enable auto-renewal.
    #3
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns1.opodo.com, ns2.opodo.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
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, 19 ms, authoritativenoyes / yesrefused2026.10.2
ns2.opodo.com 162.159.1.226NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
ns2.opodo.com 2400:cb00:2049:1::a29f:1e2NOERROR, 18 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 2417614188 · primary ns1.opodo.com

Found

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

Serial per nameserver

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

Checks

  • ✓ Serial 2417614188 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 2417614188 is a Unix timestamp (2046-08-11 15:29 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

10 records at the apex

Found

Read from
162.159.0.243:53
TypeValueTTL
SOAns1.opodo.com. dns.cloudflare.com. 2417614188 10000 2400 604800 18001800
NSns1.opodo.com.86400
NSns2.opodo.com.86400
A34.141.6.21260
MX5 alt1.aspmx.l.google.com.600
MX5 alt2.aspmx.l.google.com.600
TXT"facebook-domain-verification=928l4iuci9vjhrjugj96jy4t1oedul"600
TXT"google-site-verification=Ey00nAuq4IrpXEyWOaeUI9tBjSqaJQ53g_175nOCLYU"600
TXT"google-site-verification=Oe0T-9wrpCRiK3Rs8Y0pbvw2_eBXmnZlYWFA2DTzUHc"600
TXT"v=spf1 include:spf-a.odigeo.com include:spf-b.odigeo.com include:u1941612.wl.sendgrid.net ip4:82.150.225.79 ip4:206.17.168.27 ip4:62.23.35.22 mx ?include:trustpilotservice.com ~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. The NS TTL at the parent is 1h and in the zone 1d; resolvers may use either.
    #32
  • ✓ 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