Skip to content
https://blissagency.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
6
PASS
10
INFO
0
Probed from Amsterdam, Netherlands
403 Forbidden
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: 2606:4700:3034::6815:927, 2606:4700:3031::ac43:8d70
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:3034::6815:927]:443: connect: no route to host
IPv6 Misconfigured
AAAA Records 2606:4700:3034::6815:927, 2606:4700:3031::ac43:8d70 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.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 172.67.141.112: lookup 172.67.141.112: 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.21.9.39: lookup 104.21.9.39: 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:3034::6815:927: lookup 2606:4700:3034::6815:927: 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:3031::ac43:8d70: lookup 2606:4700:3031::ac43:8d70: 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
59 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

59
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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A
DNS Records
2 A records, 220 ms lookup
PASS
2 A records, 220 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.141.112, 104.21.9.39
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3034::6815:927, 2606:4700:3031::ac43:8d70
Info::
2 nameserver(s) configured
Got: grace.ns.cloudflare.com, wells.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (220 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 220 ms
A172.67.141.112, 104.21.9.39
AAAA2606:4700:3034::6815:927, 2606:4700:3031::ac43:8d70
CNAME—
NSgrace.ns.cloudflare.com, wells.ns.cloudflare.com
MX
10 mx10.antispam.mailspamprotection.com
20 mx20.antispam.mailspamprotection.com
30 mx30.antispam.mailspamprotection.com
TXT
SPF v=spf1 +a +mx include:blissagency.it.spf.auto.dnssmarthost.net ~all
CAALookup not available with standard resolver
Resolved in 220 ms

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 15ms across 3 resolvers (spread 28ms)
PASS
Mean 15ms across 3 resolvers (spread 28ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Quad9: 10ms
Got: 10ms via 9.9.9.9:53
Info::
Google: 32ms
Got: 32ms via 8.8.8.8:53
A+
Redirect Chain
0 redirect(s), 77 ms total
PASS
0 redirect(s), 77 ms total

https://blissagency.it

77 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://blissagency.it40377 msHTTP/1.1cloudflare
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 336 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references 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

robots.txt 200 OK
Size 336 B Sitemaps referenced 3 User-agents * Blocking No — crawling allowed
# STARTBLISS BLOCK FOR CRAWLER
# ---------------------------
User-agent: *
Disallow: /wp-admin/
Disallow: /wp-includes/
Crawl-delay: 10

Sitemap: https://blissagency.it/sitemap_index.xml
Sitemap: https://blissagency.it/post-sitemap.xml
Sitemap: https://blissagency.it/page-sitemap.xml

# ---------------------------
# END SPIDER BLOCK
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

403https://www.blissagency.it/
200https://blissagency.it/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
blissagency.it — via ARUBA-REG, 3 years, 6 months old
PASS
blissagency.it — via ARUBA-REG, 3 years, 6 months old
Info::
Domain registered until Jan 23, 2027 (6 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

195 days

January 23, 2027

SSL certificate

59 days

Issued by Google Trust Services

Domain age

3 years, 6 months

Registered January 23, 2023

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3034::6815:927

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 23, 2023 (3 years, 6 months ago)
Expires January 23, 2027 (6 months)
Last Updated February 8, 2026
Name Servers grace.ns.cloudflare.com, wells.ns.cloudflare.com
Registrant Acri Francesco
Hosting
IP Address 2606:4700:3034::6815:927
Data source: whois (0.4s)

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 47 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
9 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.
9 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
46 ms
Total Time Total request time from DNS lookup through full response.
47 ms

Connection waterfall

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

Send Feedback