Skip to content
https://farmaciamarotta.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
7 PASS 10 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).
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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 100.24.208.97 does not match any cert SAN: staticip2.multiscreensite.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 35.172.94.1 does not match any cert SAN: staticip.multiscreensite.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.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.farmaciamarotta.com/
200https://farmaciamarotta.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://farmaciamarotta.com/ → https://www.farmaciamarotta.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
C
CDN & Delivery
Action
Assets on AWS CloudFront (host irp.cdn-website.com, 17 assets); document served directly from origin (AWS)
REVIEW
Assets on AWS CloudFront (host irp.cdn-website.com, 17 assets); document served directly from origin (AWS)
Warning::
Document not behind existing CDN (AWS CloudFront serves the assets)
The page's subresources are delivered by AWS CloudFront (irp.cdn-website.com, 17 assets), but the HTML document itself comes straight from the origin (AWS). Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: x-amz-cf-id: DkyeqjTSL0oFo4ANszTSXe3eHy9DyHI0pXrt3QxF26Lf7G-GJwdFYA==
Info::
Assets on AWS CloudFront: irp.cdn-website.com (assets: 17), cache Hit from cloudfront
Got: x-amz-cf-id: DkyeqjTSL0oFo4ANszTSXe3eHy9DyHI0pXrt3QxF26Lf7G-GJwdFYA==
Info::
Assets on AWS CloudFront: iol-website.italiaonline.it (assets: 10), cache Hit from cloudfront
Got: delegation dw3zmm73bdwsn.cloudfront.net
Info::
Assets on AWS CloudFront: static.cdn-website.com (assets: 3), cache Hit from cloudfront
Got: x-amz-cf-id: Wnl8uQjn5aHLW7Y1mlkvJ9LznRmcJmBmXedxEZ9v4BGlPF8lWa857g==
Warning: Assets on a CDN, document is not: AWS CloudFront
Document origin AWS

Asset hosts on a CDN

  • irp.cdn-website.com — AWS CloudFront · assets: 17 · Cache Status: Hit from cloudfront
  • iol-website.italiaonline.it — AWS CloudFront · assets: 10 · Cache Status: Hit from cloudfront
  • static.cdn-website.com — AWS CloudFront · assets: 3 · Cache Status: Hit from cloudfront

Other asset hosts

  • consent.cookiebot.com — assets: 2 · below probe threshold
  • bcontact.paginegialle.it — assets: 1 · below probe threshold
  • consentcdn.cookiebot.com — assets: 1 · below probe threshold
  • ms-cdn.multiscreensite.com — assets: 1 · below probe threshold
  • www.googletagmanager.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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
2 A records, 42 ms lookup
PASS
2 A records, 42 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 100.24.208.97, 35.172.94.1
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns2.register.it, ns1.register.it
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 42 ms
Got: 42 ms
A100.24.208.97, 35.172.94.1
AAAA—
CNAME—
NSns2.register.it, ns1.register.it
MX
10 mail.register.it
TXT
SPF v=spf1 include:spf.webapps.net ~all
CAALookup not available with standard resolver
Resolved in 42 ms
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 52ms across 3 resolvers (spread 14ms)
PASS
Mean 52ms across 3 resolvers (spread 14ms)
Info::
Quad9: 45ms
Got: 45ms via 9.9.9.9:53
Info::
Google: 53ms
Got: 53ms via 8.8.8.8:53
Info::
Cloudflare: 59ms
Got: 59ms via 1.1.1.1:53
A
Redirect Chain
1 redirect(s), 423 ms total
PASS
1 redirect(s), 423 ms total
Info::
Single redirect
Got: https://farmaciamarotta.com → https://www.farmaciamarotta.com/ (301)
Info::
WWW normalization redirect

https://farmaciamarotta.com

326 ms · HTTP/1.1

301

https://www.farmaciamarotta.com/

97 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://farmaciamarotta.com301326 msHTTP/1.1nginx
2https://www.farmaciamarotta.com/20097 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 167 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 167 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# Sitemap is also available on /sitemap.xml
Sitemap: https://www.farmaciamarotta.com/sitemap.xml
User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=yes
sitemap.xml 200 OK
Type URL Set URLs 4 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
farmaciamarotta.com — via Register SPA, 7 days old, hosted on AWS
PASS
farmaciamarotta.com — via Register SPA, 7 days old, hosted on AWS
Info::
Domain registered until Nov 4, 2027 (11 months remaining)
Info::
Domain is only 7 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Nov 4, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Register SPA
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: AWS
Got: AS14618
Domain expiry

357 days

November 4, 2027

SSL certificate

82 days

Issued by Let's Encrypt

Domain age

7 days

Registered November 4, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

100.24.208.97

Registrar

Register SPA

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Register SPA
Created November 4, 2026 (7 days ago)
Expires November 4, 2027 (11 months)
Last Updated November 4, 2026
Name Servers ns1.register.it, ns2.register.it
DNSSEC Not enabled
Hosting
IP Address 100.24.208.97
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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

Connection waterfall

DNS Lookup 54 ms TCP Connect 109 ms TLS Handshake 108 ms Server Processing 120 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback