Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DMulti-Resolver DNS SpeedActionMean 325ms across 3 resolvers (spread 858ms)FIX
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS0/4 IPs match cert SANREVIEW
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations105 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records4 A records, 41 ms lookupPASS
| A | 52.222.201.32, 52.222.201.97, 52.222.201.88, 52.222.201.105 |
| AAAA | — |
| CNAME | — |
| NS | ns-1945.awsdns-51.co.uk, ns-1360.awsdns-42.org, ns-351.awsdns-43.com, ns-819.awsdns-38.net |
| MX | 10 hermes.paginegialle.it |
| TXT | google-site-verification=N1qg9lZm0tpgNHqcycNio9Lls8IYMmG5Zn7f20walec SPF v=spf1 ip4:141.206.150.48/29 ip4:213.209.10.46 ip4:213.209.10.47 a:relay.pagineg... |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
ARedirect Chain1 redirect(s), 203 ms totalPASS
https://paginebianche.it
76 ms · HTTP/1.1
https://www.paginebianche.it/
127 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://paginebianche.it | 301 | 76 ms | HTTP/1.1 | Apache |
| 2 | https://www.paginebianche.it/ | 200 | 127 ms | HTTP/1.1 | Apache |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 36 URLsPASS
User-agent: *
Disallow: /deu/
Disallow: /inmemoria/
Disallow: *qs=*
Disallow: *dv=*
Disallow: *sede=*
Disallow: *pref=*
Disallow: *cap=*
Disallow: /index_*.html
Disallow: /ricerca?
Disallow: /ricerca-mappa?
Disallow: /persone?
Disallow: /mappa-persone?
Disallow: /aziende?
Disallow: /mappa-aziende?
Disallow: /numeri-verdi?
Disallow: /contents/it
Disallow: /social/paginebianche/toolbar?
Disallow: /box-scheda-others?
User-agent: Yandexbot
Disallow: /
User-agent: Baiduspider
Disallow: /
User-agent: PetalBot
Disallow: /
User-agent: dotbot
Disallow: /
User-agent: dotbot/1.0
Disallow: /
User-agent: MegaIndex.ru
Disallow: /
User-agent: GPTBot
Crawl-delay: 10
User-agent: OAI-SearchBot
Crawl-delay: 10
User-agent: ClaudeBot
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: Meta-ExternalAgent
Disallow: /
User-agent: facebookexternalhit
Crawl-delay: 10
User-agent: cohere-ai
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: Applebot
Crawl-delay: 10
User-agent: Applebot-Extended
Disallow: /
User-agent: Grok
Crawl-delay: 10
User-agent: CCBot
Crawl-delay: 10
Sitemap: https://www.paginebianche.it/sitemap.xml
Sitemap: https://www.paginebianche.it/sitemap_fe.xml
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_sch...
- https://www.paginebianche.it/sitemap_nom...
- https://www.paginebianche.it/sitemap_nom...
- https://www.paginebianche.it/sitemap_nom...
- https://www.paginebianche.it/sitemap_nom...
- https://www.paginebianche.it/sitemap_nom...
- https://www.paginebianche.it/sitemap_nom...
- https://www.paginebianche.it/sitemap_nom...
- https://www.paginebianche.it/sitemap_nom...
- https://www.paginebianche.it/sitemap_nom...
- https://www.paginebianche.it/sitemap_nom...
- https://www.paginebianche.it/sitemap_fe....
- https://www.paginebianche.it/sitemap_fre...
A+Domain Intelligencepaginebianche.it — via REGISTER-REG, 27 years, 2 months old, hosted on AWSPASS
264 days
April 2, 2027
105 days
Issued by Amazon
27 years, 2 months
Registered September 30, 1999
Status unknown
Protects against DNS spoofing
AWS
ASN AS16509
52.222.201.97
REGISTER-REG
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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