Skip to content
https://Bookmakerbonus.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 10 REVIEW
C
DNSSEC
Action
Zone signed but parent has no DS record
REVIEW
Zone signed but parent has no DS record
Warning::
DNSSEC keys published but parent zone has no DS record
The zone publishes DNSKEY records but the registry has not been updated with the corresponding DS record. From a validating resolver's perspective the domain is unsigned. Submit the DS record to your registrar to complete the delegation.
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.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 15.161.6.47 does not match any cert SAN: ec2-15-161-6-47.eu-south-1.compute.amazonaws.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 277 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your 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

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 277 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# robots.txt for https://bookmakerbonus.it/

# live - don't allow web crawlers to index cpresources/ or vendor/

User-agent: *
Disallow: /cpresources/
Disallow: /vendor/
Disallow: /.env
Disallow: /ricevi/
Disallow: /visita/
Disallow: /affiliate-link-check 
Disallow: /bigquery/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

71
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
C
CDN & Delivery
Action
Assets on Fastly (host bookmakerbonus-it.imgix.net, 80 assets); document served directly from origin (AWS)
REVIEW
Assets on Fastly (host bookmakerbonus-it.imgix.net, 80 assets); document served directly from origin (AWS)
Warning::
Document not behind existing CDN (Fastly serves the assets)
The page's subresources are delivered by Fastly (bookmakerbonus-it.imgix.net, 80 assets), but the HTML document itself comes straight from the origin (AWS). Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: delegation dualstack.com.imgix.map.fastly.net
Info::
Assets on Fastly: bookmakerbonus-it.imgix.net (assets: 80), cache MISS, MISS
Got: delegation dualstack.com.imgix.map.fastly.net
Warning: Assets on a CDN, document is not: Fastly
Document origin AWS

Asset hosts on a CDN

  • bookmakerbonus-it.imgix.net — Fastly · assets: 80 · Cache Status: MISS, MISS

Other asset hosts

  • www.googletagmanager.com — assets: 2 · below probe threshold
  • static.hotjar.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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.
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: connection error.
A+
DNS Records
1 A records, 82 ms lookup
PASS
1 A records, 82 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 15.161.6.47
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns2.loopia.se, ns1.loopia.se
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 82 ms
Got: 82 ms
A15.161.6.47
AAAA—
CNAME—
NSns2.loopia.se, ns1.loopia.se
MX
10 mailcluster.loopia.se
20 mail2.loopia.se
TXT
SPF v=spf1 include:spf.loopia.se -all
CAALookup not available with standard resolver
Resolved in 82 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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 73ms across 3 resolvers (spread 32ms)
PASS
Mean 73ms across 3 resolvers (spread 32ms)
Info::
Google: 53ms
Got: 53ms via 8.8.8.8:53
Info::
Cloudflare: 83ms
Got: 83ms via 1.1.1.1:53
Info::
Quad9: 85ms
Got: 85ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://Bookmakerbonus.it

https://Bookmakerbonus.it

118 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Bookmakerbonus.it200118 msHTTP/1.1nginx
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)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

301http://Bookmakerbonus.it/ → https://bookmakerbonus.it/

Consistent

A+
Domain Intelligence
Bookmakerbonus.it — via REGISTER-REG, 9 years, 11 months old, hosted on AWS
PASS
Bookmakerbonus.it — via REGISTER-REG, 9 years, 11 months old, hosted on AWS
Info::
Domain registered until Aug 24, 2027 (9 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: AWS
Got: AS16509
Domain expiry

286 days

August 24, 2027

SSL certificate

71 days

Issued by Let's Encrypt

Domain age

9 years, 11 months

Registered January 19, 2017

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

15.161.6.47

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 January 19, 2017 (9 years, 11 months ago)
Expires August 24, 2027 (9 months)
Last Updated September 9, 2026
Name Servers ns1.loopia.se, ns2.loopia.se
Registrant WS Group AB
Hosting
IP Address 15.161.6.47
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
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 206 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
60 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
28 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
33 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
149 ms
Total Time Total request time from DNS lookup through full response.
207 ms

Connection waterfall

DNS Lookup 60 ms TCP Connect 28 ms TLS Handshake 33 ms Server Processing 28 ms Content Transfer 58 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback