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
85
GRADE
B
FIX
1
REVIEW
6
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 6 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2600:9000:203b:fa00:13:5c01:7cc0:93a1, 2600:9000:203b:1000:13:5c01:7cc0:93a1, 2600:9000:203b:1a00:13:5c01:7cc0:93a1, 2600:9000:203b:bc00:13:5c01:7cc0:93a1, 2600:9000:203b:4e00:13:5c01:7cc0:93a1, 2600:9000:203b:2c00:13:5c01:7cc0:93a1, 2600:9000:203b:4000:13:5c01:7cc0:93a1, 2600:9000:203b:6a00:13:5c01:7cc0:93a1
Info::
IPv6 connection error
Got: dial tcp6 [2600:9000:203b:fa00:13:5c01:7cc0:93a1]:443: i/o timeout
IPv6 Misconfigured
AAAA Records 2600:9000:203b:fa00:13:5c01:7cc0:93a1, 2600:9000:203b:1000:13:5c01:7cc0:93a1, 2600:9000:203b:1a00:13:5c01:7cc0:93a1, 2600:9000:203b:bc00:13:5c01:7cc0:93a1, 2600:9000:203b:4e00:13:5c01:7cc0:93a1, 2600:9000:203b:2c00:13:5c01:7cc0:93a1, 2600:9000:203b:4000:13:5c01:7cc0:93a1, 2600:9000:203b:6a00:13:5c01:7cc0:93a1 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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/12 IPs match cert SAN
REVIEW
0/12 IPs match cert SAN
Info::
PTR for 143.204.194.6 does not match any cert SAN: server-143-204-194-6.cdg54.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 143.204.194.46 does not match any cert SAN: server-143-204-194-46.cdg54.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 143.204.194.17 does not match any cert SAN: server-143-204-194-17.cdg54.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 143.204.194.87 does not match any cert SAN: server-143-204-194-87.cdg54.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 lookup failed for 2600:9000:203b:fa00:13:5c01:7cc0:93a1: lookup 2600:9000:203b:fa00:13:5c01:7cc0:93a1: 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 2600:9000:203b:1000:13:5c01:7cc0:93a1: lookup 2600:9000:203b:1000:13:5c01:7cc0:93a1: 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 2600:9000:203b:1a00:13:5c01:7cc0:93a1: lookup 2600:9000:203b:1a00:13:5c01:7cc0:93a1: 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 2600:9000:203b:bc00:13:5c01:7cc0:93a1: lookup 2600:9000:203b:bc00:13:5c01:7cc0:93a1: 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 2600:9000:203b:4e00:13:5c01:7cc0:93a1: lookup 2600:9000:203b:4e00:13:5c01:7cc0:93a1: 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 2600:9000:203b:2c00:13:5c01:7cc0:93a1: lookup 2600:9000:203b:2c00:13:5c01:7cc0:93a1: 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 2600:9000:203b:4000:13:5c01:7cc0:93a1: lookup 2600:9000:203b:4000:13:5c01:7cc0:93a1: 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 2600:9000:203b:6a00:13:5c01:7cc0:93a1: lookup 2600:9000:203b:6a00:13:5c01:7cc0:93a1: 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
TLS Certificate Expiry & Recommendations
134 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

134
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
4 A records, 35 ms lookup
PASS
4 A records, 35 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 143.204.194.6, 143.204.194.46, 143.204.194.17, 143.204.194.87
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:203b:fa00:13:5c01:7cc0:93a1, 2600:9000:203b:1000:13:5c01:7cc0:93a1, 2600:9000:203b:1a00:13:5c01:7cc0:93a1, 2600:9000:203b:bc00:13:5c01:7cc0:93a1, 2600:9000:203b:4e00:13:5c01:7cc0:93a1, 2600:9000:203b:2c00:13:5c01:7cc0:93a1, 2600:9000:203b:4000:13:5c01:7cc0:93a1, 2600:9000:203b:6a00:13:5c01:7cc0:93a1
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: d15iaiwkwkgfeb.cloudfront.net
Info::
4 nameserver(s) configured
Got: ns-1162.awsdns-17.org, ns-1797.awsdns-32.co.uk, ns-870.awsdns-44.net, ns-318.awsdns-39.com
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: 35 ms
Got: 35 ms
A143.204.194.6, 143.204.194.46, 143.204.194.17, 143.204.194.87
AAAA2600:9000:203b:fa00:13:5c01:7cc0:93a1, 2600:9000:203b:1000:13:5c01:7cc0:93a1, 2600:9000:203b:1a00:13:5c01:7cc0:93a1, 2600:9000:203b:bc00:13:5c01:7cc0:93a1, 2600:9000:203b:4e00:13:5c01:7cc0:93a1, 2600:9000:203b:2c00:13:5c01:7cc0:93a1, 2600:9000:203b:4000:13:5c01:7cc0:93a1, 2600:9000:203b:6a00:13:5c01:7cc0:93a1
CNAMEd15iaiwkwkgfeb.cloudfront.net
NSns-1162.awsdns-17.org, ns-1797.awsdns-32.co.uk, ns-870.awsdns-44.net, ns-318.awsdns-39.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 35 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: d15iaiwkwkgfeb.cloudfront.net
A+
Multi-Resolver DNS Speed
Mean 41ms across 3 resolvers (spread 44ms)
PASS
Mean 41ms across 3 resolvers (spread 44ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 39ms
Got: 39ms via 1.1.1.1:53
Info::
Quad9: 64ms
Got: 64ms 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://aziende.virgilio.it

https://aziende.virgilio.it

250 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://aziende.virgilio.it200250 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 129 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 129 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *

Disallow: /ricercalocale/*

Disallow: /ita/ricerca-aziende/*  

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 redirects to HTTPS permanently
Got: HTTP 301

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, 3 months old, hosted on MATRIX-AS - Italiaonline S.p.A., IT
PASS
virgilio.it — via ITNET-REG, 26 years, 3 months old, hosted on MATRIX-AS - Italiaonline S.p.A., IT
Info::
Domain registered until May 10, 2027 (8 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

256 days

May 10, 2027

SSL certificate

134 days

Issued by Sectigo Limited

Domain age

26 years, 3 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, 3 months ago)
Expires May 10, 2027 (8 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 (0.9s)

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 319 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 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.
261 ms
Total Time Total request time from DNS lookup through full response.
320 ms

Connection waterfall

DNS Lookup 51 ms TCP Connect 16 ms TLS Handshake 21 ms Server Processing 172 ms Content Transfer 59 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: CDG54-P1)
Got: x-amz-cf-id: Hdc64xKVpsxzmgToWw1BABwwtickx-I_uVxVrvHtKwx98TOBc2rD2g==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: Hdc64xKVpsxzmgToWw1BABwwtickx-I_uVxVrvHtKwx98TOBc2rD2g==
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