Skip to content
https://seoriented.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
2
REVIEW
6
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 6 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 549ms across 3 resolvers (spread 1519ms)
FIX
Mean 549ms across 3 resolvers (spread 1519ms)
Info::
Google: 37ms
Got: 37ms via 8.8.8.8:53
Info::
Cloudflare: 56ms
Got: 56ms via 1.1.1.1:53
Info::
Quad9: 1556ms
Got: 1556ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 1519ms (min 37ms / max 1556ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 37.156.244.10 does not match any cert SAN: mercurio.vhosting-it.com
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 2a0c:79c0:3:a::4 does not match any cert SAN: mercurio.vhosting-it.com
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.
B
TLS Certificate Expiry & Recommendations
56 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

56
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
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, 63 ms lookup
PASS
1 A records, 63 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 37.156.244.10
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a0c:79c0:3:a::4
Info::
5 nameserver(s) configured
Got: sdns3.vhosting-it.com, sdns2.vhosting-it.com, sdns4.vhosting-it.com, sdns1.vhosting-it.com, mercurio.vhosting-it.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 63 ms
Got: 63 ms
A37.156.244.10
AAAA2a0c:79c0:3:a::4
CNAME—
NSsdns3.vhosting-it.com, sdns2.vhosting-it.com, sdns4.vhosting-it.com, sdns1.vhosting-it.com, mercurio.vhosting-it.com
MX
10 mailserver10.vhosting-it.com
TXT
caa=managed
SPF v=spf1 +a +mx +ip4:37.156.244.10 +ip6:2a0c:79c0:3:a::4 include:relay.vhosting-it...
CAALookup not available with standard resolver
Resolved in 63 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

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 | issuewild: comodoca.com, digicert.com, letsencrypt.org
PASS
issue: comodoca.com, digicert.com, letsencrypt.org | issuewild: comodoca.com, digicert.com, letsencrypt.org
Info::
CAA issue tag present — authorized CA(s): comodoca.com, digicert.com, letsencrypt.org
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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://seoriented.it

https://seoriented.it

96 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://seoriented.it20096 msHTTP/1.1LiteSpeed
A+
IPv6 Readiness
IPv6 reachable (28 ms)
PASS
IPv6 reachable (28 ms)
Info::
IPv6 is configured and reachable at 2a0c:79c0:3:a::4
Got: 28 ms connect
IPv6 Ready
AAAA Records 2a0c:79c0:3:a::4 Connection Reachable (28 ms)
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 272 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 272 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

Allow: /wp-admin/admin-ajax.php

Disallow: /vai/

Disallow: /corsi/

Disallow: /hosting/

Disallow: /libro/

Disallow: /*?page_id=

Disallow: /*?pag=

Disallow: /*?s=

Disallow: /*?p=


Sitemap: https://seoriented.it/sitemap_index.xml
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 301-redirects to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
seoriented.it — via VHOSTINGSRL-REG, 6 years, 8 months old
PASS
seoriented.it — via VHOSTINGSRL-REG, 6 years, 8 months old
Info::
Domain registered until Nov 25, 2026 (4 months remaining)
Info::
Registrar: VHOSTINGSRL-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

134 days

November 25, 2026

SSL certificate

56 days

Issued by Let's Encrypt

Domain age

6 years, 8 months

Registered November 25, 2019

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a0c:79c0:3:a::4

Registrar

VHOSTINGSRL-REG

Unlocked 4 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 VHOSTINGSRL-REG
Created November 25, 2019 (6 years, 8 months ago)
Expires November 25, 2026 (4 months)
Last Updated December 11, 2025
Name Servers sdns1.vhosting-it.com, sdns3.vhosting-it.com, sdns2.vhosting-it.com, web.mercurio.vhosting-it.com
Registrant Jacopo Curletto
Hosting
IP Address 2a0c:79c0:3:a::4
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 227 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 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.
31 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
221 ms
Total Time Total request time from DNS lookup through full response.
228 ms

Connection waterfall

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

Send Feedback