Skip to content
https://sportbet.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
302 Found
Checks
17
9 PASS 7 REVIEW 1 FIX
D
Redirect Chain
Action
3 redirect(s), 461 ms total
FIX
3 redirect(s), 461 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
3-hop chain could be reduced to 1 hop
Redirect directly from https://sportbet.it to https://www.sportbet.it/home
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://sportbet.it

https://sportbet.it

145 ms · HTTP/1.1

302

http://www.sportbet.it/

109 ms · HTTP/1.1

302

https://www.sportbet.it/

83 ms · HTTP/1.1

301

https://www.sportbet.it/home

124 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://sportbet.it302145 msHTTP/1.1cloudflare
2http://www.sportbet.it/302109 msHTTP/1.1cloudflare
3https://www.sportbet.it/30183 msHTTP/1.1cloudflare
4https://www.sportbet.it/home200124 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://sportbet.it to https://www.sportbet.it/home

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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.20.31.127: lookup 104.20.31.127: 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 172.66.160.245: lookup 172.66.160.245: 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
87 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
2 A records, 52 ms lookup
PASS
2 A records, 52 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.20.31.127, 172.66.160.245
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: carla.ns.cloudflare.com, julian.ns.cloudflare.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 52 ms
Got: 52 ms
A104.20.31.127, 172.66.160.245
AAAA—
CNAME—
NScarla.ns.cloudflare.com, julian.ns.cloudflare.com
MX
10 cloudscan8.ilger.com
20 cloudscan9.ilger.com
TXT
google-site-verification=ZUkx917_UvvkzrEWufoeYgxc6ayhN-5WzdtEovU3yek
SPF v=spf1 a mx include:spf.turbo-smtp.com include:spf.webapps.net include:spf.mobil...
CAALookup not available with standard resolver
Resolved in 52 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 39ms across 3 resolvers (spread 52ms)
PASS
Mean 39ms across 3 resolvers (spread 52ms)
Info::
Cloudflare: 19ms
Got: 19ms via 1.1.1.1:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
Info::
Quad9: 71ms
Got: 71ms via 9.9.9.9:53
A+
Crawlability
robots.txt present, sitemap with 1879 URLs
PASS
robots.txt present, sitemap with 1879 URLs
Info::
robots.txt is present
Got: 22 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1879 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 22 B Sitemaps referenced 0 User-agents * Allow: / Blocking No — crawling allowed
User-agent: * Allow: /
sitemap.xml 200 OK
Type URL Set URLs 1879 entries Valid XML Yes
Sample URLs:
A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Warning::
HTTP→HTTPS redirect is not permanent
Got: HTTP 302 Expected: 301 or 308 permanent redirect

www / non-www

301https://www.sportbet.it/
200https://sportbet.it/

Preferred variant: non-www

HTTP → HTTPS

302http://sportbet.it/ → https://sportbet.it/

Use a permanent redirect (301 or 308) instead of a temporary one

A+
Domain Intelligence
sportbet.it — via REGISTER-REG, 26 years, 4 months old, hosted on Cloudflare
PASS
sportbet.it — via REGISTER-REG, 26 years, 4 months old, hosted on Cloudflare
Info::
Domain registered until Jul 21, 2027 (10 months remaining)
Info::
Registrar: REGISTER-REG
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

324 days

July 21, 2027

SSL certificate

87 days

Issued by Google Trust Services

Domain age

26 years, 4 months

Registered September 14, 2000

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

172.66.160.245

Registrar

REGISTER-REG

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar REGISTER-REG
Created September 14, 2000 (26 years, 4 months ago)
Expires July 21, 2027 (10 months)
Last Updated August 6, 2026
Name Servers julian.ns.cloudflare.com, carla.ns.cloudflare.com
Registrant SPORTBET S.R.L.
Hosting
IP Address 172.66.160.245
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: whois (0.8s)

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 166 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
34 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.
21 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
166 ms
Total Time Total request time from DNS lookup through full response.
167 ms

Connection waterfall

DNS Lookup 34 ms TCP Connect 17 ms TLS Handshake 21 ms Server Processing 94 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a333390c5ec3d0ae-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a333390c5ec3d0ae-CDG
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback