VirusTotal
5 / 91
“우리 가계부”
private-household-ledger.pages.dev returned HTTP status 200 on 2026-10-01, per the recorded HTTP check. The same evidence set records an internal listing on the PhishDestroy list, a signal separate from the HTTP response.
The domain was first observed on 2026-09-16. External blocklists recorded three listings dated to the blocklist check on 2026-10-01: MetaMask, SEAL, and PhishFeed. VirusTotal recorded 5 detections across 91 scanners on 2026-09-29. The SSL scan on 2026-09-21 identified Google Trust Services / WE1 as the issuer. The page performance score was 55 on 2026-09-21.
The MetaMask, SEAL, and PhishFeed listings and the PhishDestroy internal listing were recorded on dates distinct from the VirusTotal scan, so the counts reflect separate collection points rather than one simultaneous snapshot. The HTTP status and SSL observations likewise come from different dates, meaning a reader can compare the records but cannot treat them as a single current state.
Reviewers should retain the dated records for private-household-ledger.pages.dev, including the blocklist and VirusTotal entries, so later observations can be compared against them. Any follow-up check should note the exact date and source, and reviewers should avoid submitting sensitive information while examining the domain.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
0bc439b6d2d2972731ba10cb9b6f4c5dfded998c2dfd25cd7351fe6f92fd5ab4Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of private-household-ledger.pages.dev · checked Sep 21, 2026
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
151 stored lookalike domains
Showing 100 of 151
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
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