← Back to browse

Yatori

The future of payments

Crypto

yatori.io · Added June 18, 2026 · Last analysed June 18, 2026 · via Hacker News · 62% 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 18 June 2026; the live site may have changed since.

Yatori is largely in shape, with complete legal pages and a thorough launch checklist. Main gaps: missing several security headers, no sitemap, and incomplete email security.

Launched on Hacker News on June 18, 2026. The site is hosted on Amazon.com in the United States. The crawl picked up 8 technologies on this site, covering CSS frameworks, DNS providers, business email, and frameworks. The stack includes Nuxt, Tailwind CSS, and Vue.js.

For context, it's one of 31 launches on this exact stack.

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

Vibe Score 0 · No AI signals
Informational pattern-match signal. Does not feed the StackScope Score. See which fingerprints fired →

Tech Stack (8)

Infrastructure
DNS GoDaddy DNS
Hosting Vercel
Security HSTS
Email
Business email Google Workspace
Build & Framework
CSS framework Tailwind CSS
Framework Vue.js
Meta-framework Nuxt
Analytics & Marketing
SEO Google Search Console

Infrastructure

Network
AS16509 · US
DNS
GoDaddy DNS
Authoritative nameserver
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
SSL Certificate
Let's Encrypt
Valid 17 Jun 2026 to 15 Sep 2026
Certificate as captured in this snapshot, not a live check.

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.

Storage (0)

This site uses no client-side storage we could detect on page load.

Readiness Breakdown How?

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

Performance How?

256 ms Server response
63% Faster than peers
1304 ms Largest contentful paint
0.00 Cumulative layout shift
8.0 MB Page weight
7.5 MB Image weight
1 Third-party domains
0 Console errors
0 Failed requests

12 images: 9 oversized, 12 without width/height

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

AI Stance

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

Well-Known Files

sitemap.xml
security.txt
llms.txt
ads.txt
humans.txt
90% unique

Security Headers (1/6)

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

Build

2 JS files
8 CSS files
1 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.