← Back to browse

Agentsxbackend

One word, three problems: one burns tokens, one double-charges the customer, and one nobody has cleanly solved.

Games

Added June 30, 2026 · Last analysed June 30, 2026 · via Hacker News · 40% unique tagline (similar to Which AI agent are you?)

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 30 June 2026; the live site may have changed since.

Agentsxbackend has the basics covered well, with complete legal pages, a thorough launch checklist, and well-configured email security. What needs work: missing several security headers, no robots.txt or sitemap, and tracking cookies set before any opt-in.

Launched on Hacker News on June 30, 2026. The site is served through Cloudflare, with a domain registered in 2010. Our crawler found 14 technologies on this site, covering security, ui library, analytics, and backend framework. The stack includes Amazon Web Services, Cloudflare, and Cloudflare Bot Management.

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

Vibe Score 15 · Few 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 (14) · Scale-up stack

Infrastructure
CDN Cloudflare (2)
Cloud Amazon Web Services
Protocol HTTP/3
Security Cloudflare Bot Management
HSTS
Build & Framework
Font Google Fonts
JavaScript library React Router
UI library Lucide Icons
shadcn/ui
Analytics & Marketing
Analytics Segment
Publishing Substack (5)
SEO Norton Safe Web
Business Tools
Error tracking Sentry (2)
Other
Backend framework Express

Infrastructure

Network
AS13335 · US
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
Green hosting
Green hosted
Host runs on renewable energy. Data from The Green Web Foundation.
SSL Certificate
Google Trust Services
Valid 24 May 2026 to 22 Aug 2026
Certificate as captured in this snapshot, not a live check.
Domain Age
16.2 years
Registered Apr 2010 · Amazon Registrar, Inc.

Email Security

SPF ~all (via apex substack.com) Soft-fail (~all). Common and accepted.
DKIM (via apex substack.com) Detected on apex substack.com
DMARC p=reject (via apex substack.com) Reject (strict). Strong.
?
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.

Storage (15)

Cookies (9)
NameLifetimeDetected as
ab_experiment_sampled 1y Substack
ajs_anonymous_id 1y Segment
AWSALBTG 7d Amazon Web Services
AWSALBTGCORS 7d -
cf_clearance 1y Cloudflare
cookie_storage_key 3mo -
disable_experiments session Substack
disable_html_pixels session Substack
__cf_bm < 1h Cloudflare
Local storage (4)
KeySizeDetected as
pub-9722747-subscribe-prompt-next-shown-at 13 B Substack
pub-9722747-takeover-next-shown-at 13 B Substack
substack_ref 2 B Substack
substack_ref_url 75 B Substack
Session storage (2)
KeySizeDetected as
substack_ref 2 B Substack
substack_ref_url 75 B Substack

Readiness Breakdown How?

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

Performance How?

292 ms Server response
57% Faster than peers
1280 ms Largest contentful paint
0.00 Cumulative layout shift
3.6 MB Page weight
919 KB Image weight
5 Third-party domains
1 Console errors
1 Failed requests

10 images: 1 without width/height, 5 missing alt text

Broken first-party requests (1), worth fixing
  • 401 /api/v1/reporting/flows

Indicative grade from a single automated render, not a substitute for Lighthouse or field data, and not part of the StackScope score.

Vibe Score Breakdown How?

SignalPoints
AI CSS signals +10
AI palette signals +5

This score is based on structural patterns and is not definitive. Many legitimate sites may trigger signals, and AI-built sites may go undetected. It should be treated as an indicator, not a verdict.

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
sitemap.xml
security.txt
llms.txt
ads.txt
humans.txt
Privacy Policy
/privacy
Terms of Service
/tos
? Consent manager not detected
Analytics set tracking cookies on our visit, with no opt-in step.

Security Headers (3/6)

X-Frame-Options via CSP frame-ancestors
Permissions-Policy experimental (check browser support)
X-XSS-Protection deprecated (use Content-Security-Policy)

Build

Code splitting
198 JS files
27 CSS files
5 Third-party domains

Brand Colours

Something not look right? If a technology shown here is wrong or out of date, email [email protected] and we'll review it.