Skip to content
https://Retelit.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Madrid, Spain
302 Found
Checks
17
7 PASS 10 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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 194.244.12.9: lookup 194.244.12.9: 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.
B
Multi-Resolver DNS Speed
Mean 73ms across 3 resolvers (spread 191ms)
REVIEW
Mean 73ms across 3 resolvers (spread 191ms)
Info::
Quad9: 5ms
Got: 5ms via 9.9.9.9:53
Info::
Cloudflare: 20ms
Got: 20ms via 1.1.1.1:53
Info::
Google: 196ms
Got: 196ms via 8.8.8.8:53
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
141 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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 Bunny CDN (host cdn.eye-able.com, 3 assets); document served directly from origin
REVIEW
Assets on Bunny CDN (host cdn.eye-able.com, 3 assets); document served directly from origin
Warning::
Document not behind existing CDN (Bunny CDN serves the assets)
The page's subresources are delivered by Bunny CDN (cdn.eye-able.com, 3 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 eye-able.b-cdn.net
Info::
Assets on Bunny CDN: cdn.eye-able.com (assets: 3)
Got: delegation eye-able.b-cdn.net
Info::
Assets on Akamai: consent.cookiebot.com (assets: 3)
Got: delegation consent.cookiebot.com-v2.edgekey.net
Warning: Assets on a CDN, document is not: Bunny CDN
Document origin not attributed

Asset hosts on a CDN

  • cdn.eye-able.com — Bunny CDN · assets: 3
  • consent.cookiebot.com — Akamai · assets: 3

Other asset hosts

  • www.googletagmanager.com — assets: 3 · Google
  • fonts.googleapis.com — assets: 2 · below probe threshold
  • consentcdn.cookiebot.com — assets: 1 · below probe threshold
  • snap.licdn.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: 404.
A
DNS Records
1 A records, 203 ms lookup
PASS
1 A records, 203 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 194.244.12.9
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: danica.ns.cloudflare.com, denver.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (203 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 203 ms
A194.244.12.9
AAAA—
CNAME—
NSdanica.ns.cloudflare.com, denver.ns.cloudflare.com
MX
10 retelit-it.mail.protection.outlook.com
TXT
SPF v=spf1 include:mail.spf.retelit.it include:mail.spf.irideos.it include:spf.prote...
MS=ms16174867
PlzbgH8DdL4jg3r1RGfabDOsY++PhKmAZyLvZdL+Yazesvt3QMEIPbDNEUpb6MZwOB1+qnCORspxj9nN...
google-site-verification=sko3O10L-u5eMNd-4Fdm6wnMoPVUsqIwz4iolZt6_7Y
CAALookup not available with standard resolver
Resolved in 203 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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
Redirect Chain
1 redirect(s), 838 ms total
PASS
1 redirect(s), 838 ms total
Info::
Single redirect
Got: https://Retelit.it → https://Retelit.it/it/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://Retelit.it
Info::
Redirect overhead: 838 ms total
Got: 838 ms

https://Retelit.it

206 ms · HTTP/1.1

302

https://Retelit.it/it/

632 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Retelit.it302206 msHTTP/1.1nginx
2https://Retelit.it/it/200632 msHTTP/1.1nginx

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+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 171 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 171 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://retelit.it/it/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
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

302https://www.Retelit.it/
200https://Retelit.it/

Preferred variant: non-www

HTTP → HTTPS

301http://Retelit.it/ → https://retelit.it/

Consistent

A
Domain Intelligence
Retelit.it — via PLY-REG, 21 years, 10 months old, hosted on AS-RETELIT-IRIDEOS - Retelit Digital Services S.p.A., IT
PASS
Retelit.it — via PLY-REG, 21 years, 10 months old, hosted on AS-RETELIT-IRIDEOS - Retelit Digital Services S.p.A., IT
Warning::
Domain expires in 40 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Dec 17, 2026
Info::
Registrar: PLY-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: AS-RETELIT-IRIDEOS - Retelit Digital Services S.p.A., IT
Got: AS3302
Domain expiry

38 days

December 17, 2026

SSL certificate

141 days

Issued by DigiCert Inc

Domain age

21 years, 10 months

Registered April 15, 2005

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AS-RETELIT-IRIDEOS - Retelit Digital Services S.p.A., IT

ASN AS3302

194.244.12.9

Registrar

PLY-REG

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar PLY-REG
Created April 15, 2005 (21 years, 10 months ago)
Expires December 17, 2026 (1 months)
Last Updated January 2, 2026
Name Servers danica.ns.cloudflare.com, denver.ns.cloudflare.com
Registrant Retelit S.p.A.
Hosting
IP Address 194.244.12.9
ASN AS3302 (AS-RETELIT-IRIDEOS - Retelit Digital Services S.p.A., IT)
Provider AS-RETELIT-IRIDEOS - Retelit Digital Services S.p.A., IT
Data source: whois (0.7s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

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

Send Feedback