← Back to browse

TearMate — Find someone to cry with

Find someone to cry with

Added April 10, 2026 · Last analysed April 10, 2026 · via · 50% 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.

TearMate — Find someone to cry with is missing several launch fundamentals. Main gaps: missing several security headers, no robots.txt or sitemap, and incomplete email security.

Launched on Product Hunt on April 10, 2026. The site is hosted on GitHub Pages and served through Fastly. Our crawler found 5 technologies on this site, covering CDN, DNS providers, email forwarding, and web fonts. The stack includes Fastly, GitHub Pages, and Google Fonts.

It's also on one of the most common stacks we track, shared by 1,758 launches.

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

Vibe Score 40 · Some 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 Fastly (2)
DNS Namecheap DNS
Hosting GitHub Pages (2)
Email
Email forwarding Namecheap Email Forwarding (2)
Build & Framework
Font Google Fonts

Infrastructure

Network
AS54113 · US
DNS
Namecheap DNS
Authoritative nameserver
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
SSL Certificate
Let's Encrypt
Valid 9 Apr 2026 to 8 Jul 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.

Readiness Breakdown How?

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

Vibe Score Breakdown How?

SignalPoints
Placeholder branding +10
AI writing signals +5
AI code-structure 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.html
Terms of Service
/terms.html
80% unique

Security Headers (0/6)

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

Performance

143ms response time
Faster than 84% of sites
1 third-party domains loaded

Build

0 JS files
1 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.