Cloudflare Radar
Scan report
Open reportThe page at familyfinances-ledger.netlify.app displays a household ledger login interface prompting users to select a profile and enter a passcode. Do not enter any passcodes or personal credentials into this portal.
Page title: “Our Money Ledger”
Listed by external blocklists: MetaMask, SEAL, PhishFeed. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Cloudflare Radar capture · 2026-11-18 19:37 UTC · SHA-256 e69009a5…0140e6b
PhishDestroy analysis, reviewed version
The page hosted on familyfinances-ledger.netlify.app presents a clean, minimalist sign-in card centered against a pale background. At the top, bold serif typography displays the headline "Our Money Ledger", followed by the explanatory subtitle "Sign in once on each phone or computer. It stays signed in." Below this text, the form asks the visitor "WHO'S THIS?" and provides two preset profile selection buttons labeled "Pomi" and "Nati". Finally, a prominent gradient button at the bottom invites the visitor to click "Sign in" to complete the authentication process while requesting a "HOUSEHOLD PASSCODE". Because MetaMask, SEAL and PhishFeed block it, this passcode-collection interface is recognized as a risk rather than a legitimate service. The domain still answered requests on 18 Nov 2026 at 20:26 UTC.
When a visitor types a shared passcode into the "HOUSEHOLD PASSCODE" field and clicks the gradient "Sign in" button, any entered secrets are transmitted directly to the site operator. Because the interface mimics a personal financial ledger while running on public netlify.app infrastructure, visitors are tricked into disclosing confidential access keys. This unauthorized collection puts any connected shared financial accounts or household systems at immediate risk of compromise by whoever controls the portal.
Anyone who has already typed a passcode into this interface should immediately change related household account passwords and monitor associated financial services for unauthorized access. Because the domain was first flagged on 18 Nov 2026, users should verify that their actual financial software and ledgers remain secure and completely disconnected from this portal.
Scan report
Open reportPage capture
SHA-256 e94c4b97…8ce1d15
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
10 / 100 · heuristic score · 1 brand reference · 0 classifications
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | Spf lookups: 0 |
|---|---|
| Caa records | Count: 3; Domain: netlify.app; Issuers: digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226, amazon.com |
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Page title and metadata | Title: Our Money Ledger; Themecolor: #F7E9E7 |
| Trackers | Requests: 4; Trackers: (Name: Google Fonts; Company: Google; Country: US; Category: Hosting; Requests: 1) |
| Forms and mixed content | Third party scripts: 0 |
| Status | Up: ✓; Code: 200; Timings: DNS: 0; Wait: 324; Download: 6; Response ms: 453 |
| TLS connection | Alpn: h2; Cipher: TLS_AES_128_GCM_SHA256; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓ |
| Ports | Open: 80, 443 |
| Carbon | Bytes: 51499; Co2 grams: 0.0019; Cleaner than: 36 |
| DNS server | NS: (IP: 198.51.44.1; Host: dns1.p01.nsone.net), (IP: 198.51.45.1; Host: dns2.p01.nsone.net), (IP: 198.51.44.65; Host: dns3.p01.nsone.net), (IP: 198.51.45.65; Host: dns4.p01.nsone.net); Zone: netlify.app |
| Quality | Cls: 0.026; Seo: 90; Si s: 2.56; Fcp s: 2.56; Lcp s: 2.56; Tbt ms: 0; Performance: 93; Accessibility: 97; Best practices: 96 |
| Location | IP: 2a05:d014:58f:6200::259; ASN: 16509; Org: Amazon.com, Inc.; City: Frankfurt; Country: DE |
| SSL | San: *.netlify.app, netlify.app; Bits: 256; Chain: *.netlify.app, DigiCert Global G2 TLS RSA SHA256 2020 CA1, DigiCert Global Root G2; Issuer: DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1; Serial: 0CD5D0AFB0611B5BD9D692535C0CA7C4; SHA256: bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478; Subject: *.netlify.app; Valid to: 2027-03-19T23:59:59Z; Valid from: 2026-02-16T00:00:00Z |
| DNS records | A: 35.157.26.135, 63.176.8.218; Aaaa: 2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258 |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Header: max-age=31536000; includeSubDomains; preload; Message: Site is compatible with the HSTS preload list!; Compatible: ✓ |
| HTTP security policies | Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: max-age=31536000; includeSubDomains; preload; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Get IP | IP: 2a05:d014:58f:6200::258; Family: 6 |
| Redirects | Chain: https://familyfinances-ledger.netlify.app |
| HTTP headers | Headers: Server: Netlify; Content type: text/html; charset=UTF-8; Strict transport security: max-age=31536000; includeSubDomains; preload |
No official connection links this site to established ledger services. The domain runs on netlify.app, and MetaMask, SEAL and PhishFeed block it.
You should change your shared passcodes immediately across all connected household devices and services to prevent unauthorized access. Entering credentials here exposes your accounts to whoever controls the portal.
Because MetaMask, SEAL and PhishFeed block it, automated feeds classify the login portal as a potential risk. The domain still answered requests on 18 Nov 2026 at 20:26 UTC while serving this unauthorized sign-in form.
Last checked
Edge-IP reputation is not attributed to this domain.
dns1.p01.nsone.netdns2.p01.nsone.netdns3.p01.nsone.netdns4.p01.nsone.netLocation describes the IP network.
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478*.netlify.appnetlify.appSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was serving its pages at the latest check.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Google PageSpeed Insights — mobile performance audit of familyfinances-ledger.netlify.app ·
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 16 SHA-256 hashes: 15 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-18 19:28 UTC.
Open this scan on URLScan 01a1f01e-e27f-71a9-9315-9a0bef7741c2 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Serving page content
page content returned
Reachable
Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
151 stored lookalike domains
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
A similar name alone does not prove fraud. Send the list to services that check each address themselves. Report a domain as phishing only if you saw a fake page on it.
Where to send it:
Nothing matches. Clear the search or choose another filter.
Showing 12 of 151
Showing 100 of 151
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
familyfinances-ledger.netlify.app Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
familyfinances-ledger.netlify.app)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.