Skip to content
https://shopaccino.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
8 PASS 8 REVIEW 1 FIX
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).
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 167.99.69.4: lookup 167.99.69.4: 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 2400:6180:0:d1::418:e001: lookup 2400:6180:0:d1::418:e001: 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
Redirect Chain
1 redirect(s), 1300 ms total
REVIEW
1 redirect(s), 1300 ms total
Info::
Single redirect
Got: https://shopaccino.com → https://www.shopaccino.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1300 ms total
Got: 1300 ms

https://shopaccino.com

505 ms · HTTP/1.1

301

https://www.shopaccino.com/

795 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://shopaccino.com301505 msHTTP/1.1Apache/2.4.62 (Ubuntu)
2https://www.shopaccino.com/200795 msHTTP/1.1Apache/2.4.62 (Ubuntu)

See the visual redirect chain in the HTTP Probe tab →

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.shopaccino.com/
200https://shopaccino.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://shopaccino.com/ → https://shopaccino.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
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: connection error, /health: 404, /healthz: 404, /ping: connection error, /status: connection error.
A+
DNS Records
1 A records, 111 ms lookup
PASS
1 A records, 111 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 167.99.69.4
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: 2400:6180:0:d1::418:e001
Info::
3 nameserver(s) configured
Got: ns3.digitalocean.com, ns2.digitalocean.com, ns1.digitalocean.com
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 111 ms
Got: 111 ms
A167.99.69.4
AAAA2400:6180:0:d1::418:e001
CNAME—
NSns3.digitalocean.com, ns2.digitalocean.com, ns1.digitalocean.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
google-site-verification=nYbgQf4Vby6zaRmb_UqwpbY7KzcK-kisgkmfcvLXaqc
1phYumQAR0ynLnhXSQfkA8TmlnkSd4YTh0DdxjrpSDE=
SPF v=spf1 include:sendgrid.net include:_spf.google.com ~all
_globalsign-domain-verification=nSg8fqQKmsz5oAoyBpyCT3JR4vBtfUYWMGvTEthdtm
google-site-verification=fJGckmyQicTuJw6Pn7BwImEj09xQcrQQOBrWjDqZg20
CAALookup not available with standard resolver
Resolved in 111 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: globalsign.com, letsencrypt.org | issuewild: globalsign.com, letsencrypt.org
PASS
issue: globalsign.com, letsencrypt.org | issuewild: globalsign.com, letsencrypt.org
Info::
CAA issue tag present — authorized CA(s): globalsign.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
Multi-Resolver DNS Speed
Mean 66ms across 3 resolvers (spread 54ms)
PASS
Mean 66ms across 3 resolvers (spread 54ms)
Info::
Cloudflare: 48ms
Got: 48ms via 1.1.1.1:53
Info::
Google: 49ms
Got: 49ms via 8.8.8.8:53
Info::
Quad9: 102ms
Got: 102ms via 9.9.9.9:53
A+
IPv6 Readiness
IPv6 reachable (240 ms)
PASS
IPv6 reachable (240 ms)
Info::
IPv6 is configured and reachable at 2400:6180:0:d1::418:e001
Got: 240 ms connect
IPv6 Ready
AAAA Records 2400:6180:0:d1::418:e001 Connection Reachable (240 ms)
A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 98 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 98 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# Allows all robots


User-agent: *

Disallow:


Sitemap: https://www.shopaccino.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 4 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
shopaccino.com — via PDR Ltd. d/b/a PublicDomainRegistry.com, 12 years, 4 months old
PASS
shopaccino.com — via PDR Ltd. d/b/a PublicDomainRegistry.com, 12 years, 4 months old
Info::
Domain registered until Jun 24, 2027 (9 months remaining)
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: PDR Ltd. d/b/a PublicDomainRegistry.com
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

294 days

June 24, 2027

SSL certificate

71 days

Issued by Let's Encrypt

Domain age

12 years, 4 months

Registered June 24, 2014

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2400:6180:0:d1::418:e001

Registrar

PDR Ltd. d/b/a PublicDomainRegistry.com

Unlocked 3 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar PDR Ltd. d/b/a PublicDomainRegistry.com
Created June 24, 2014 (12 years, 4 months ago)
Expires June 24, 2027 (9 months)
Last Updated May 29, 2026
Name Servers ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
DNSSEC Not enabled
Hosting
IP Address 2400:6180:0:d1::418:e001
Data source: rdap (1.2s)

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

Connection waterfall

DNS Lookup 58 ms TCP Connect 169 ms TLS Handshake 172 ms Server Processing 170 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