← Back to browse

SceneCaption Studio

SceneCaption Studio connects local Whisper transcription, scene cut detection, subtitle timing edits, and Final Cut Pro export in one macOS workflow.

Content

stunning-crumble-49af3e.netlify.app · Added June 20, 2026 · Last analysed June 20, 2026 · via · 78% 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 20 June 2026; the live site may have changed since.

SceneCaption Studio still has work before launch. Visible gaps: missing several security headers, incomplete legal pages, and no robots.txt or sitemap.

Launched on Product Hunt on June 20, 2026. The site is hosted on Amazon.com in the United States. The crawl picked up 2 technologies on this site, covering hosting and security. The stack includes HSTS and Netlify.

For context, it's on one of the most common stacks we track, shared by 1,171 launches.

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

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

Tech Stack (2)

Infrastructure
Hosting Netlify
Security HSTS

Infrastructure

Network
AS16509 · US
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
SSL Certificate
DigiCert Inc
Valid 16 Feb 2026 to 19 Mar 2027
Certificate as captured in this snapshot, not a live check.

Email Security

SPF Not published. Your domain can be spoofed in phishing emails.
?
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
Responsive viewport meta tag
Semantic HTML (nav, main, article)
- Open Graph tags (title, image, description)
- Canonical URL declared
- Twitter card meta tags
- Favicon present

Performance How?

500 ms Server response
36% Faster than peers
1132 ms Largest contentful paint
0.00 Cumulative layout shift
10.6 MB Page weight
10.6 MB Image weight
0 Console errors
0 Failed requests

5 images: 5 oversized, 5 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.

Vibe Score Breakdown How?

SignalPoints
Placeholder branding +10
AI onboarding 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 not detected
? Terms of Service not detected
Detection works best on English language sites.

Security Headers (1/6)

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

Build

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