Skip to content
https://Giocodigitale.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
9
PASS
8
INFO
0
Probed from Santa Clara, United States
302 Found
Checks
17
8 PASS 9 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.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 195.72.134.91 does not match any cert SAN: redirex.itsfogo.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.
Info::
PTR for 195.72.135.91 does not match any cert SAN: backgammon.betoto.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

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 7754 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 7754 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed


<!DOCTYPE html>
<!--[if lt IE 9]>      <html class="preload no-js oldie" data-srvid="130.130.253"> <![endif]-->
<!--[if gt IE 8]><!-->
<html class="preload no-js" data-srvid="130.130.253">
<!--<![endif]-->
<head>
    <title>Aiuto - Siamo spiacenti di informarti che il tuo indirizzo IP è stato bloccato</title>
    <!--[if lt IE 9]><script src="/HelpV3/Web/scripts/modernizr.js"></script><![endif]-->
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta content="width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0, user-scalable=no" name="viewport">
<meta content="noindex, nofollow" name="robots">
<link rel="apple-touch-icon" sizes="180x180" href="-/media/ED4E5EB3474446D79DBE0257DFB1DDEF.ashx">
<link rel="icon" type="image/png" sizes="32x32" href="-/media/7255372374914F6BB62291C894CD5567.ashx">
<link rel="icon" type="image/png" sizes="16x16" href="-/media/7AE8FACB8CFE4FF6ABBA270C831E18AB.ashx">
<link rel="shortcut icon" href="-/media/639562D5E10A4FCC8BD33632405DC247.ashx">
<link href="https://scmedia.giocodigitale.it/$-$/2049b547f8094d75821ec2abfc39e8e9.css" rel="stylesheet" type="text/css" />

    <link href="https://fonts.googleapis.com/css?family=Roboto+Condensed:400,700&subset=latin,greek,cyrillic" rel="stylesheet" type="text/css">
    
    <!--[if gt IE 8]>
    <style type="text/css">
        #m-navigation #option-list li {

            display: inline-block\0;
            width: 33%\0;
        }
    </style>
    <!--<![endif]-->
</head>
<body class="cf active-content">

    <header class="header">
        <div class="regulatory-header">
            
        </div>
        <menu role="menubar" class="navigation-menu top-menu cf">
            <nav class="menu-left">
                <a href="#" class="theme-help-menu"></a>
            </nav>
                <div id="search-icon">
                    <span class="theme-search">
                    </span>
                </div>
            <h2>
                <a href="http://help.giocodigitale.it/closed"><img src="https://scmedia.giocodigitale.it/$-$/75b4e75df05b454e895b96095ed81c31.png" alt="" width="132" height="27" /><span></span></a>
            </h2>
            <nav class="menu-right">
                <a href="#" class="theme-close-i"></a>
            </nav>
        </menu>
    </header>



        <form id="search-form" onkeypress="return event.keyCode != 13;">
            <div class="search-bar">
                <div class="overlay"></div>

                <div class="search-fields">
                    <input id="searchInput" autofocus type="text" placeholder="Cerca temi di aiuto" data-lang="it" data-virtual-lang="" />
                </div>

                <div class="search-results">
                    <ul class="search-result-list" id="searchresultlist"></ul>

                    <div class="toggle-collapsible">
                        <div class="theme-toggle-button" id="searchResultToggle"></div>
                    </div>
                </div>
            </div>
        </form>

    <menu role="menu" class="navigation-menu sub-menu" style="display: block">
        <nav class="menu-left">
            <a href="#" class="theme-left" id="innerBack" data-depth="1"></a>
        </nav>
        <header>
            <h2>Siamo spiacenti di informarti che il tuo indirizzo IP è stato bloccato</h2>
        </header>
    </menu>
        <nav role="navigation" class="navigation main-navigation" style="display: block;">
            
        </nav>
            <div role="main" class="main" style="display: block;">
            <div class="wrapper cf">
                <a id="top"></a>


                    <section id="secTNC" class="content">
        <article>


            <style type="text/css">
    #search-form, nav.menu-left, #search-icon, .navigation-menu.sub-menu, nav.navigation.main-navigation, #language-switch {display:none!important}
    div.main {margin:0 auto !important; width:100%!important;}
    section.content {max-width:800px!important; margin: 0 auto !important; float:none !important; border:none!important;}    
</style>
<p><img height="261" alt="blocked-bwin" width="725" src="https://media.itsfogo.com/media/sccmsupload/Vanilla/Whitelabel/App/Help/blocked-bwin.jpg"></p>
<p>Caro visitatore!</p>
<p>Purtroppo i servizi di questo sito non sono più disponibili per i clienti residenti nel tuo paese. Di conseguenza, non è possibile accedere ai nostri siti dalla tua attuale locazione. Inoltre, non accettiamo più versamenti o la partecipazione ai giochi dalla giurisdizione da cui hai provato a registrarti o a effettuare il login. Se disponi di un conto in denaro vero, il tuo saldo è ancora accessibile e puoi prelevarlo inoltrandone richiesta a <a href="mailto:info@giocodigitale.it">info@giocodigitale.it</a>. L'esclusione è dovuta all'indirizzo IP del computer da cui accedi al nostro sito, che indica la tua locazione.</p>
<p>Siamo spiacenti di comunicarti che siamo attualmente tenuti a bloccare il tuo accesso al sito fintanto che continuerai ad accedervi da questo paese.</p>

<p>Il team Gioco Digitale </p>
<p> </p>
<h2>Domande frequenti (FAQ)</h2>
<h3>Come potete sapere dove mi trovo attualmente?</h3>
<p>Il nostro software individua la tua attuele posizione sulla base del tuo indirizzo IP. Nel caso in cui l'indirizzo IP possa essere ricondotto al tuo paese, siamo purtroppo obbligati ad escluderti dall'utilizzo del nostro programma di giochi.</p>
<h3>Che cos'è un indirizzo IP?</h3>
<p>Un indirizzo IP è un indirizzo dei network informatici basato sul protocollo internet (IP), proprio come internet. Ogni computer che accede a internet può essere chiaramente identificato da questa combinazione di numeri (in cui  numeri sono sempre separati da tre punti, come in 179.89.72.9).</p>
<h3>Quanto è affidabile la tecnologia Geo-IP ?</h3>
<p>Purtroppo, la tecnologia Geo-IP non garantisce una precisione al 100% nel determinare la tua posizione. Miglioriamo continuamente la precisione della tecnologia Geo-IP con continui aggiornamenti. Se non sei stato correttamente identificato dal software Geo-IP e risulti essere in un paese che non corrisponde alla tua effettiva posizione, o ti trovi in un paese che non è escluso dai nostri prodotti, contatta il nostro Servizio clienti per contribuire all'ulteriore miglioramento della precisione del nostro sistema di tecnologia Geo-IP.</p>
<p> </p>
<p><style type="text/css">.pm-area-navigation{display:none!important}.container{width:100%;max-width:740px;margin:0 auto}#header{width:100%}#header .header-bar{width:auto; display: none}#main-wrap{width:100%;max-width:740px;padding:10px 1% 10px 1%;-moz-box-sizing:border-box;-webkit-box-sizing:border-box;-ms-box-sizing:border-box;box-sizing:border-box}.sub-navigation{width:100%;max-width:700px;overflow:hidden;display:none}#main{width:100%}.pm-nav-layout .pm-area-main{width:100%}.pm-area-main>div.pm-widget-box{margin-right:0}.text>p>img{display:block;margin:0 auto;height:auto}#footer{width:98%;padding:0 1%}#footer .copyright{width:50%;max-width:740px;margin-top:-10px;float:right}.language-switch{width:25%;margin-top:0}#footer .meta-navigation{width:25%;margin-left:0}#footer .meta-navigation>ul#footer-navigation{position:static}#footer .language-switch .selector{width:100px}</style></p>

        </article>
    </section>
            </div>
        </div>



    <script type="text/javascript">
        var preLoadedResults =null;
var min = 3;var max = 30;    </script>

    <script src="https://scmedia.giocodigitale.it/$-$/c978548368b041ff851dfe3eee7258b9.js" type="text/javascript">

</script>



    


</body>
</html>
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
153 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

153
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 Cloudflare (host scmedia.giocodigitale.it, 5 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host scmedia.giocodigitale.it, 5 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (scmedia.giocodigitale.it, 5 assets), but the HTML document itself comes straight from the origin. 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 scmedia.giocodigitale.it.cdn.cloudflare.net
Info::
Assets on Cloudflare: scmedia.giocodigitale.it (assets: 5), cache HIT
Got: delegation scmedia.giocodigitale.it.cdn.cloudflare.net
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • scmedia.giocodigitale.it — Cloudflare · assets: 5 · Cache Status: HIT

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.
A+
DNS Records
2 A records, 10 ms lookup
PASS
2 A records, 10 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 195.72.134.91, 195.72.135.91
Info::
No IPv6 (AAAA) records
Info::
8 nameserver(s) configured
Got: dns1.itsbogo.com, dns1.itsfogo.com, dns2.itsbogo.com, dns2.itsfogo.com, dns3.itsfogo.com, dns4.itsfogo.com, dns5.itsfogo.com, dns6.itsfogo.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 10 ms
Got: 10 ms
A195.72.134.91, 195.72.135.91
AAAA—
CNAME—
NSdns1.itsbogo.com, dns1.itsfogo.com, dns2.itsbogo.com, dns2.itsfogo.com, dns3.itsfogo.com, dns4.itsfogo.com, dns5.itsfogo.com, dns6.itsfogo.com
MX
10 mailgate01.itsfogo.com
10 mailgate02.itsfogo.com
TXT
MS=ms33390559
e3bc191f3ec79815
_5zfrhe196dqmme8v7kpq2jtxvd2v51t
_iixtv3lwforh9au2z1b94zktt4wckmb
_mjyd4735auzsjpmgo45jka4wrk7lkth
_s1wdhk8u3tqjgjofp0l51158ddr3gtw
dg5czyc2jx21rgfzk77fdrwx1htr0tbv
fgg723g8qjyvmjf51kpbkskr5xgc4n03
lzq6x4j7wpvwlfxgckxjhgp3vmvtb8lw
lzwsm7mzks4kx01g33ycdx3b1n58kysy
zj5m6kh0b9zcy0cfnhqsbz7yxwldbq9n
SFMC-O5vt58AVZGwcy_v1k3P0Hes4_9BvOd2fnvntLlaA
Validity-rVPc47ada323KiwlsAHguipzLx9167JH0zTtJ
google-site-verification=d7-54m5OfMlxQQBPsdy4OmortdXJg2pfsAEBRmCslv0
SPF v=spf1 include:_spf.itsfogo.com include:mail.zendesk.com include:spf.protection....
CAALookup not available with standard resolver
Resolved in 10 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 6ms across 3 resolvers (spread 9ms)
PASS
Mean 6ms across 3 resolvers (spread 9ms)
Info::
Quad9: 3ms
Got: 3ms via 9.9.9.9:53
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Google: 12ms
Got: 12ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 425 ms total
PASS
1 redirect(s), 425 ms total
Info::
Single redirect
Got: https://Giocodigitale.it → https://help.giocodigitale.it/closed (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://Giocodigitale.it
Info::
Cross-domain redirect detected

https://Giocodigitale.it

173 ms · HTTP/1.1

302

https://help.giocodigitale.it/closed

252 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Giocodigitale.it302173 msHTTP/1.1
2https://help.giocodigitale.it/closed200252 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

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

A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect is not permanent
Got: HTTP 302 Expected: 301 or 308 permanent redirect

www / non-www

403https://www.Giocodigitale.it/
200https://Giocodigitale.it/

HTTP → HTTPS

302http://Giocodigitale.it/ → https://help.giocodigitale.it/closed

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

A+
Domain Intelligence
Giocodigitale.it — via COMLAUDE-REG, 20 years, 2 months old, hosted on BETANDWIN-AS - Entain Services Austria GmbH, AT
PASS
Giocodigitale.it — via COMLAUDE-REG, 20 years, 2 months old, hosted on BETANDWIN-AS - Entain Services Austria GmbH, AT
Info::
Domain registered until Jun 11, 2027 (9 months remaining)
Info::
Registrar: COMLAUDE-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: BETANDWIN-AS - Entain Services Austria GmbH, AT
Got: AS13008
Domain expiry

272 days

June 11, 2027

SSL certificate

153 days

Issued by DigiCert Inc

Domain age

20 years, 2 months

Registered October 17, 2006

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

BETANDWIN-AS - Entain Services Austria GmbH, AT

ASN AS13008

195.72.135.91

Registrar

COMLAUDE-REG

Unlocked 6 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 COMLAUDE-REG
Created October 17, 2006 (20 years, 2 months ago)
Expires June 11, 2027 (9 months)
Last Updated June 27, 2026
Name Servers dns1.itsfogo.com, dns2.itsfogo.com, dns3.itsfogo.com, dns4.itsfogo.com, dns5.itsfogo.com, dns6.itsfogo.com
Registrant Eurobet Italia srl Unipersonale
Hosting
IP Address 195.72.135.91
ASN AS13008 (BETANDWIN-AS - Entain Services Austria GmbH, AT)
Provider BETANDWIN-AS - Entain Services Austria GmbH, AT
Data source: whois (0.6s)

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 501 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
7 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
158 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
161 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
501 ms
Total Time Total request time from DNS lookup through full response.
502 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 158 ms TLS Handshake 161 ms Server Processing 175 ms Content Transfer 0 ms
A+
Health Check Endpoint
Health endpoint at https://Giocodigitale.it/health (HTTP 200)
PASS
Health endpoint at https://Giocodigitale.it/health (HTTP 200)
Info::
Public health endpoint at https://Giocodigitale.it/health
Got: https://Giocodigitale.it/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback