Skip to content
https://aziende.virgilio.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 7 REVIEW 1 FIX
F
HTTP Probe Timing
Action
Total 9300 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
93 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
9.25 s
Total Time Total request time from DNS lookup through full response.
9.30 s

Connection waterfall

DNS Lookup 93 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 9.15 s Content Transfer 50 ms
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/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR for 52.222.132.129 does not match any cert SAN: server-52-222-132-129.mad53.r.cloudfront.net
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 52.222.132.68 does not match any cert SAN: server-52-222-132-68.mad53.r.cloudfront.net
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 52.222.132.74 does not match any cert SAN: server-52-222-132-74.mad53.r.cloudfront.net
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 52.222.132.89 does not match any cert SAN: server-52-222-132-89.mad53.r.cloudfront.net
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
TLS Certificate Expiry & Recommendations
173 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

173
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
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
4 A records, 37 ms lookup
PASS
4 A records, 37 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 52.222.132.129, 52.222.132.68, 52.222.132.74, 52.222.132.89
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: d39n3avh1kgnms.cloudfront.net
Info::
4 nameserver(s) configured
Got: ns-1336.awsdns-39.org, ns-1832.awsdns-37.co.uk, ns-347.awsdns-43.com, ns-734.awsdns-27.net
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 37 ms
Got: 37 ms
A52.222.132.129, 52.222.132.68, 52.222.132.74, 52.222.132.89
AAAA—
CNAMEd39n3avh1kgnms.cloudfront.net
NSns-1336.awsdns-39.org, ns-1832.awsdns-37.co.uk, ns-347.awsdns-43.com, ns-734.awsdns-27.net
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 37 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Subdomain Takeover
CNAME points at managed service(s) — verify configuration
PASS
CNAME points at managed service(s) — verify configuration
Info::
CNAME targets AWS CloudFront — verify ownership
CNAME targets CloudFront. Distribution names are GUID-style so accidental re-registration is unlikely, but a deleted distribution will return errors. Verify the CloudFront distribution is still active.
Got: d39n3avh1kgnms.cloudfront.net
A+
Multi-Resolver DNS Speed
Mean 20ms across 3 resolvers (spread 15ms)
PASS
Mean 20ms across 3 resolvers (spread 15ms)
Info::
Quad9: 12ms
Got: 12ms via 9.9.9.9:53
Info::
Cloudflare: 23ms
Got: 23ms via 1.1.1.1:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
A+
Redirect Chain
No redirect data available
PASS
No redirect data available
Info::
No redirect data captured
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 94 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 94 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *

Disallow: /ricercalocale/*

Sitemap: https://aziende.virgilio.it//sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 1 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::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.aziende.virgilio.it/
200https://aziende.virgilio.it/

HTTP → HTTPS

301http://aziende.virgilio.it/ → https://aziende.virgilio.it/

Consistent

A+
Domain Intelligence
virgilio.it — via ITNET-REG, 26 years, 1 months old, hosted on MATRIX-AS - Italiaonline S.p.A., IT
PASS
virgilio.it — via ITNET-REG, 26 years, 1 months old, hosted on MATRIX-AS - Italiaonline S.p.A., IT
Info::
Domain registered until May 10, 2027 (10 months remaining)
Info::
Registrar: ITNET-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: MATRIX-AS - Italiaonline S.p.A., IT
Got: AS8660
Domain expiry

301 days

May 10, 2027

SSL certificate

173 days

Issued by Sectigo Limited

Domain age

26 years, 1 months

Registered September 29, 2000

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

MATRIX-AS - Italiaonline S.p.A., IT

ASN AS8660

213.209.17.209

Registrar

ITNET-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 ITNET-REG
Created September 29, 2000 (26 years, 1 months ago)
Expires May 10, 2027 (10 months)
Last Updated May 26, 2026
Name Servers ns1.italiaonline.it, ns2.iol.it
Registrant Italiaonline S.p.A.
Hosting
IP Address 213.209.17.209
ASN AS8660 (MATRIX-AS - Italiaonline S.p.A., IT)
Provider MATRIX-AS - Italiaonline S.p.A., IT
Data source: whois (1.0s)

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
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MAD53-P7)
Got: x-amz-cf-id: I92f1c96Da8P8brO5-AGzsQaLbVkB6-N_ZsI_v_kiS8op-87LwaTHw==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: I92f1c96Da8P8brO5-AGzsQaLbVkB6-N_ZsI_v_kiS8op-87LwaTHw==
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 1 header(s)
Got: x-cache=Miss from cloudfront
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback