Skip to content
https://migliorisitiporno.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
6
PASS
11
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
11 PASS 6 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).
C
Reverse DNS
Action
0/6 IPs match cert SAN
REVIEW
0/6 IPs match cert SAN
Info::
PTR lookup failed for 104.26.0.47: lookup 104.26.0.47: 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 104.26.1.47: lookup 104.26.1.47: 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 172.67.69.197: lookup 172.67.69.197: 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 2606:4700:20::681a:12f: lookup 2606:4700:20::681a:12f: 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 2606:4700:20::681a:2f: lookup 2606:4700:20::681a:2f: 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 2606:4700:20::ac43:45c5: lookup 2606:4700:20::ac43:45c5: 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 68 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 68 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

Allow: /wp-admin/admin-ajax.php
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
59 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A+
DNS Records
3 A records, 39 ms lookup
PASS
3 A records, 39 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.0.47, 104.26.1.47, 172.67.69.197
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::681a:12f, 2606:4700:20::681a:2f, 2606:4700:20::ac43:45c5
Info::
2 nameserver(s) configured
Got: norm.ns.cloudflare.com, pola.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
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: 39 ms
Got: 39 ms
A104.26.0.47, 104.26.1.47, 172.67.69.197
AAAA2606:4700:20::681a:12f, 2606:4700:20::681a:2f, 2606:4700:20::ac43:45c5
CNAME—
NSnorm.ns.cloudflare.com, pola.ns.cloudflare.com
MX
0 _dc-mx.31bcd0c76053.migliorisitiporno.it
TXT—
CAALookup not available with standard resolver
Resolved in 39 ms

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
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
CAA Records
issue: comodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.com | issuewild: comodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.com
PASS
issue: comodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.com | issuewild: comodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.com
Info::
CAA issue tag present — authorized CA(s): comodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.com
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Multi-Resolver DNS Speed
Mean 27ms across 3 resolvers (spread 7ms)
PASS
Mean 27ms across 3 resolvers (spread 7ms)
Info::
Cloudflare: 24ms
Got: 24ms via 1.1.1.1:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
Info::
Quad9: 31ms
Got: 31ms 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://migliorisitiporno.it

https://migliorisitiporno.it

80 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://migliorisitiporno.it20080 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (26 ms)
PASS
IPv6 reachable (26 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::681a:12f, 2606:4700:20::681a:2f, 2606:4700:20::ac43:45c5
Got: 26 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::681a:12f, 2606:4700:20::681a:2f, 2606:4700:20::ac43:45c5 Connection Reachable (26 ms)
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 301-redirects to HTTPS

www / non-www

301https://www.migliorisitiporno.it/
200https://migliorisitiporno.it/

Preferred variant: non-www

HTTP → HTTPS

301http://migliorisitiporno.it/ → https://migliorisitiporno.it/

Consistent

A+
Domain Intelligence
migliorisitiporno.it — via ARUBA-REG, 13 years, 8 months old
PASS
migliorisitiporno.it — via ARUBA-REG, 13 years, 8 months old
Info::
Domain registered until Jan 16, 2027 (5 months remaining)
Info::
Registrar: ARUBA-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.
Domain expiry

177 days

January 16, 2027

SSL certificate

59 days

Issued by Google Trust Services

Domain age

13 years, 8 months

Registered January 16, 2013

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::681a:12f

Registrar

ARUBA-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 ARUBA-REG
Created January 16, 2013 (13 years, 8 months ago)
Expires January 16, 2027 (5 months)
Last Updated February 1, 2026
Name Servers norm.ns.cloudflare.com, pola.ns.cloudflare.com
Registrant MARCO FALCO
Hosting
IP Address 2606:4700:20::681a:12f
Data source: whois (0.7s)

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

Connection waterfall

DNS Lookup 47 ms TCP Connect 17 ms TLS Handshake 25 ms Server Processing 46 ms Content Transfer 17 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a1ea0cdc68e69eb9-CDG
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: a1ea0cdc68e69eb9-CDG
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=56544, cf-cache-status=HIT
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback