← Back to browse

squire

The public Squire service has been shut down.

Developer Tools

Added April 6, 2026 · Last analysed April 10, 2026 · via · 75% unique tagline

StackScope is a free public catalogue of indie launches. We find launches on Product Hunt, Hacker News and similar feeds, then crawl each site to detect its tech stack and score it for launch readiness: DNS, security headers, SEO basics. This page is what we saw on 10 April 2026; the live site may have changed since.

squire ships with the basics, with a thorough launch checklist and fast page loads. Visible gaps: no Strict-Transport-Security, incomplete legal pages, and no sitemap.

Launched on Product Hunt on April 6, 2026. The site is served through Cloudflare. We've detected 5 technologies on this site, covering CDN, DNS providers, email forwarding, and protocol. The stack includes Cloudflare, Cloudflare DNS, and Cloudflare Email Routing.

It's more locked down than the typical Product Hunt launch.

If you own this site, refresh the snapshot and see the full fix list any time →

5.8
StackScope Score
Fair
82/100 Launch Readiness
Well prepared
0/3 Legal
Missing
1/2 Crawl files
Partial
Vibe Score 0 · No AI signals
How much the site looks AI-generated. Informational pattern-match signal, not a verdict. Does not feed the StackScope Score. See which fingerprints fired →

Tech Stack (5)

Infrastructure
CDN Cloudflare (3)
DNS Cloudflare DNS
Protocol HTTP/3 (2)
Email
Email forwarding Cloudflare Email Routing (2)
Analytics & Marketing
SEO Google Search Console

Infrastructure

Network
AS13335 · US
DNS
Cloudflare DNS
Authoritative nameserver
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.

Email Security

SPF ~all Soft-fail (~all). Common and accepted.
?
DKIM Not detected at common selectors. Your provider may use a custom one.
DMARC Not published. Receivers fall back to permissive defaults.
?
MTA-STS Not deployed. Mail to your domain can be downgraded to plaintext en route.
?
TLS-RPT Not configured. You won't hear about silent SMTP TLS handshake failures.

Readiness Breakdown How?

Custom title and meta description
Open Graph tags (title, image, description)
Responsive viewport meta tag
Favicon present
Semantic HTML (nav, main, article)
- Canonical URL declared
- Twitter card meta tags

AI Stance

No AI stance declared
llms.txt published
No AI bots blocked in robots.txt
? No directive declared
? None advertised

Well-Known Files

robots.txt (no directives)
sitemap.xml
security.txt
llms.txt
ads.txt
humans.txt
? Privacy Policy not detected
? Terms of Service not detected
Detection works best on English language sites.

Security Headers (5/6)

Permissions-Policy experimental (check browser support)
X-XSS-Protection deprecated (use Content-Security-Policy)

Performance

106ms response time
Faster than 93% of sites

Build

0 JS files
1 CSS files
0 Third-party domains
Something not look right? If a technology shown here is wrong or out of date, email [email protected] and we'll review it.