Skip to content
https://all4lace.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
8 PASS 9 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.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 188.114.96.2: lookup 188.114.96.2: 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 188.114.97.2: lookup 188.114.97.2: 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 2a06:98c1:3120::2: lookup 2a06:98c1:3120::2: 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 2a06:98c1:3121::2: lookup 2a06:98c1:3121::2: 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
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.all4lace.com/
200https://all4lace.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

61
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 & Delivery
Document and assets on Cloudflare
REVIEW
Document and assets on Cloudflare
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a53123b5fe43d11c-CDG
Info::
Assets on Cloudflare: www.all4lace.com (assets: 200), cache HIT
Got: cf-ray: a531253dcaf66f27-CDG
Document served via CDN: Cloudflare
Provider Cloudflare Evidence cf-ray: a53123b5fe43d11c-CDG

Asset hosts on a CDN

  • www.all4lace.com — Cloudflare · assets: 200 · Cache Status: HIT

Other asset hosts

  • static.cloudflareinsights.com — assets: 1 · below probe threshold
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, 39 ms lookup
PASS
2 A records, 39 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 188.114.96.2, 188.114.97.2
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3120::2, 2a06:98c1:3121::2
Info::
2 nameserver(s) configured
Got: tiffany.ns.cloudflare.com, sam.ns.cloudflare.com
Info::
No MX records — email not configured via DNS
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
A188.114.96.2, 188.114.97.2
AAAA2a06:98c1:3120::2, 2a06:98c1:3121::2
CNAME—
NStiffany.ns.cloudflare.com, sam.ns.cloudflare.com
MX—
TXT
pinterest-site-verification=e4b8941c1a8f515f098b6389b1a5ba43
google-site-verification=UZuK8Tr5jUNYZMAV4bwH6yIC8GjJ9kPRX3vFWrsQZSI
google-site-verification=HsmJWvdnaeLt4WUICy_1crRqne6SATygO6ELi5RBe28
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+
Multi-Resolver DNS Speed
Mean 30ms across 3 resolvers (spread 12ms)
PASS
Mean 30ms across 3 resolvers (spread 12ms)
Info::
Cloudflare: 24ms
Got: 24ms via 1.1.1.1:53
Info::
Quad9: 31ms
Got: 31ms via 9.9.9.9:53
Info::
Google: 36ms
Got: 36ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 265 ms total
PASS
1 redirect(s), 265 ms total
Info::
Single redirect
Got: https://all4lace.com → https://www.all4lace.com/ (301)
Info::
WWW normalization redirect

https://all4lace.com

68 ms · HTTP/1.1

301

https://www.all4lace.com/

197 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://all4lace.com30168 msHTTP/1.1cloudflare
2https://www.all4lace.com/200197 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3120::2, 2a06:98c1:3121::2
Got: 17 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3120::2, 2a06:98c1:3121::2 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 3515 URLs
PASS
robots.txt present, sitemap with 3515 URLs
Info::
robots.txt is present
Got: 71 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3515 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 71 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /

Sitemap: https://www.all4lace.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 3515 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
all4lace.com — via DNSPod, Inc., 11 months old
PASS
all4lace.com — via DNSPod, Inc., 11 months old
Info::
Domain registered until Nov 21, 2027 (1 years 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: DNSPod, Inc.
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

377 days

November 21, 2027

SSL certificate

61 days

Issued by Google Trust Services

Domain age

11 months

Registered November 21, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3121::2

Registrar

DNSPod, Inc.

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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar DNSPod, Inc.
Created November 21, 2025 (11 months ago)
Expires November 21, 2027 (1 years)
Last Updated September 22, 2026
Name Servers sam.ns.cloudflare.com, tiffany.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2a06:98c1:3121::2
Data source: rdap (0.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 99 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
37 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.
21 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
99 ms
Total Time Total request time from DNS lookup through full response.
99 ms

Connection waterfall

DNS Lookup 37 ms TCP Connect 17 ms TLS Handshake 21 ms Server Processing 24 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