VirusTotal
11 / 89
On 2026-10-01, 1inch-login.com returned an HTTP status code of 502 when checked. The domain was first observed on 2026-08-26, according to the recorded evidence.
VirusTotal recorded 11 detections across 89 scanners for 1inch-login.com on 2026-09-13. OTX listed 2 pulses on 2026-09-13, and the external blocklists MetaMask and SEAL were checked on 2026-10-01 with a count of 2. The domain appears on the phishdestroy internal listing, and the registrar is Dominet (HK) Limited.
The VirusTotal and OTX observations share the 2026-09-13 date, so they describe the same point in time, while the HTTP check on 2026-10-01 and the blocklist check on 2026-10-01 reflect a later date. Because these sources were recorded on different dates, a reader can compare the earlier detection and pulse records with the later HTTP and blocklist records without treating any single source as a complete picture. The first observation on 2026-08-26 predates all of these checks, providing an earlier reference point for the domain's recorded history.
Anyone reviewing 1inch-login.com should retain the dated records from VirusTotal, OTX, and the external blocklists so that later checks can be compared against the same source values. Subsequent observations of 1inch-login.com should be recorded with their own dates and source names, allowing changes in HTTP status, detections, or listings to be tracked over time. During this review, avoid submitting sensitive information to 1inch-login.com until the recorded evidence has been fully assessed.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='1inch-login.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
wells.ns.cloudflare.comLocation describes the IP network.
12 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.
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