VirusTotal
3 / 89
The domain addi-colombia.netlify.app returned an HTTP status code 404 on 2026-10-01, indicating that no content was accessible at the requested URL during that check. This domain was also observed on multiple security blocklists and internal listings.
On 2026-10-01, addi-colombia.netlify.app appeared on the MetaMask and SEAL external blocklists. VirusTotal recorded 3 detections out of 89 scanners on 2026-09-13. The domain was first observed on 2026-08-26, and a phishdestroy internal listing was present. The HTTP 404 status was documented on 2026-10-01.
The blocklist entries from MetaMask and SEAL, along with the phishdestroy internal listing, show how several sources classified addi-colombia.netlify.app on their respective dates. VirusTotal provided additional detection information from its scan. The HTTP 404 response documents the domain’s web server behavior at a specific point in time, without indicating content status at other moments.
For addi-colombia.netlify.app, preserve the MetaMask and SEAL blocklist records, the phishdestroy internal listing, and the VirusTotal detection record for future comparison. Retain the HTTP response record for reference in subsequent reviews. Monitor updated blocklist and scanner records to track any changes in classification.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
NetlifyScanner note: http_other: raw=http_404; http=404; via=http_proxy; server=Netlify
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
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.
79 stored lookalike domains
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