Skip to content
https://Oddschecker.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
9 PASS 8 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 104.18.27.139: lookup 104.18.27.139: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.18.26.139: lookup 104.18.26.139: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
TLS Certificate Expiry & Recommendations
82 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

82
days left
0d 30d 60d 90d+

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a388e7f87c793b9c-CDG
Document served via CDN: Cloudflare
Provider Cloudflare Evidence cf-ray: a388e7f87c793b9c-CDG
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
DNS Records
2 A records, 30 ms lookup
PASS
2 A records, 30 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.27.139, 104.18.26.139
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-cloud-c4.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 30 ms
Got: 30 ms
A104.18.27.139, 104.18.26.139
AAAA—
CNAME—
NSns-cloud-c4.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com
MX
10 eu-smtp-inbound-2.mimecast.com
10 eu-smtp-inbound-1.mimecast.com
TXT
ca3-7ddd25f449db4ae0a64f5d3ea34faaf6
apple-domain-verification=rFaAtDAi55cu32FO
google-site-verification=d5r-J1fpGodeeNyQ74KKEZx8fqHFOP_JH8dy8nUDyEk
google-site-verification=tu-nTk3f46gNCNWDvyk7CF9yMsDpfyqTOGVk7vJeINaJTg
google-site-verification=hPZULGcRSCUYhyKtNqV4IBJ-pASzh6bnSQSg7WXoh_I
MS=ms76096908
google-site-verification=tu-wBLxLFW0QV-GVdCQ6nWsvVnVPo9griy3yLz4I54s
SPF v=spf1 include:_spf.google.com include:spf.protection.outlook.com ip4:90.216.131...
google-site-verification=Mj4hRTjAi_MHiJwt99nVJAziU24kEXEEZFSDvJow9WE
CAALookup not available with standard resolver
Resolved in 30 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 40ms across 3 resolvers (spread 12ms)
PASS
Mean 40ms across 3 resolvers (spread 12ms)
Info::
Quad9: 34ms
Got: 34ms via 9.9.9.9:53
Info::
Cloudflare: 41ms
Got: 41ms via 1.1.1.1:53
Info::
Google: 46ms
Got: 46ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 192 ms total
PASS
1 redirect(s), 192 ms total
Info::
Single redirect
Got: https://Oddschecker.com → https://www.oddschecker.com/ (301)
Info::
WWW normalization redirect

https://Oddschecker.com

63 ms · HTTP/1.1

301

https://www.oddschecker.com/

128 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Oddschecker.com30163 msHTTP/1.1cloudflare
2https://www.oddschecker.com/403128 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1629 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references sitemap

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt 200 OK
Size 1629 B Sitemaps referenced 19 User-agents * Blocking No — crawling allowed

User-agent: *
        
Disallow: /*/bet-history/*
Disallow: /clickout*
Disallow: /it/clickout*
Disallow: /es/clickout*
Disallow: /us/clickout*
Disallow: /br/clickout*
Disallow: /co/clickout*
Disallow: /au/clickout*
Disallow: /nz/clickout*
Disallow: /in/clickout*
Disallow: /pt/clickout*
Disallow: /za/clickout*
Disallow: /ke/clickout*
Disallow: /ng/clickout*
Disallow: /nl/clickout*
Disallow: /fr/clickout*
Disallow: /se/clickout*
Disallow: /sm/clickout*
Disallow: /cx/clickout*
Disallow: /us/football/test*
Disallow: /xx
Disallow: /*/myoddschecker/*
Disallow: /search*
Disallow: /cdn-cgi/
Disallow: /ajax-page/
Disallow: */view-all-markets/*

Sitemap: https://www.oddschecker.com/sitemap.xml
Sitemap: https://www.oddschecker.com/it/sitemap.xml
Sitemap: https://www.oddschecker.com/es/sitemap.xml
Sitemap: https://www.oddschecker.com/us/sitemap.xml
Sitemap: https://www.oddschecker.com/br/sitemap.xml
Sitemap: https://www.oddschecker.com/co/sitemap.xml
Sitemap: https://www.oddschecker.com/au/sitemap.xml
Sitemap: https://www.oddschecker.com/nz/sitemap.xml
Sitemap: https://www.oddschecker.com/in/sitemap.xml
Sitemap: https://www.oddschecker.com/pt/sitemap.xml
Sitemap: https://www.oddschecker.com/za/sitemap.xml
Sitemap: https://www.oddschecker.com/ke/sitemap.xml
Sitemap: https://www.oddschecker.com/ng/sitemap.xml
Sitemap: https://www.oddschecker.com/nl/sitemap.xml
Sitemap: https://www.oddschecker.com/fr/sitemap.xml
Sitemap: https://www.oddschecker.com/se/sitemap.xml
Sitemap: https://www.oddschecker.com/sm/sitemap.xml
Sitemap: https://www.oddschecker.com/cx/sitemap.xml
Sitemap: https://www.oddschecker.com/ca/sitemap.xml
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

403https://www.Oddschecker.com/
200https://Oddschecker.com/

HTTP → HTTPS

301http://Oddschecker.com/ → https://www.oddschecker.com/

Consistent

A+
Domain Intelligence
Oddschecker.com — via CSC Corporate Domains, Inc., 26 years, 8 months old, hosted on Cloudflare
PASS
Oddschecker.com — via CSC Corporate Domains, Inc., 26 years, 8 months old, hosted on Cloudflare
Info::
Domain registered until May 26, 2027 (8 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: CSC Corporate Domains, Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

256 days

May 26, 2027

SSL certificate

82 days

Issued by Google Trust Services

Domain age

26 years, 8 months

Registered May 26, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.26.139

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created May 26, 2000 (26 years, 8 months ago)
Expires May 26, 2027 (8 months)
Last Updated May 22, 2026
Name Servers ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com
DNSSEC Not enabled
Hosting
IP Address 104.18.26.139
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 100 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
39 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
100 ms
Total Time Total request time from DNS lookup through full response.
100 ms

Connection waterfall

DNS Lookup 39 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 20 ms Content Transfer 0 ms
A+
Health Check Endpoint
Auth-protected health endpoint at https://Oddschecker.com/health (HTTP 403)
PASS
Auth-protected health endpoint at https://Oddschecker.com/health (HTTP 403)
Info::
Auth-protected health endpoint exposed at https://Oddschecker.com/health
Got: https://Oddschecker.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback