Highscore 44 · flagged Tuesday, October 6, 2026

recoverly.dev

Appeared in the .dev zone on Tuesday, October 6, 2026; by the end of that day the census found active website. Full domain report

Signals, not verdicts. A domain appears here because heuristics matched its name, its infrastructure or the page it served on its first day. Where a model has looked at it, that is shown as an opinion with a confidence, not as a finding. Nothing on this page says a site is malicious. Read the evidence and decide for yourself.

Own one of these names and think the listing is wrong? Tell us and a person will look.

What matched

lure words (login, verify, secure…)
matched: recover
+6
brand in page title, not in the name
matched: chase
+20
form on a brand-styled page
matched: has_form
+18
Registrar
Gandi SAS
Nameserver provider
Nameservers
ns-159-c.gandi.net, ns-49-b.gandi.net, ns-9-a.gandi.net
First-day state
active website
HTTP status
200
Page title
Recoverly — failed-payment recovery for Stripe subscriptions
Has a form
yes
Brand echoed
—

Model opinions

First passsuspiciousconfidence 60%· claude-haiku-4-5

The domain has a legitimate-looking Stripe integration tool (failed-payment recovery software) with its own branding and honest disclosures about what it can/cannot do. However, the scorer flags 'brand-in-title-not-name' (Chase mentioned in page text) and 'form-on-brand-page', and the form collects work email, company name, and website before asking for Stripe API credentials. The page transparently states it will request read-only Stripe keys and explains permissions, which is normal for SaaS t

A model looked at the screenshot and page text and wrote what it thought. It can be wrong, and it is not a finding.

What the page looked like on Tuesday, October 6, 2026

Screenshot of recoverly.dev taken by the zone census on 2026-10-06

Same data as JSON: /api/zone/domain/recoverly.dev. This page is not indexed by search engines and does not link to the site it describes.