VirusTotal
11 / 89
“ldglive3.com”
ldglive3.com returned HTTP status 502 in an HTTP check recorded on 2026-10-01, a dated response that describes only that single request. The domain also appears on the phishdestroy internal listing, and its earliest observation in this evidence set is 2026-08-23.
The HTTP check on 2026-10-01 recorded status 502 for ldglive3.com. A blocklist check on 2026-10-01 counted two external blocklists, named as MetaMask and SEAL. VirusTotal recorded 11 detections across 89 scanners on 2026-09-09. OTX recorded three pulses on 2026-09-09. The registrar of record is NICENIC INTERNATIONAL GROUP CO., LIMITED.
The named sources describe different things: an HTTP response code, external blocklist presence, VirusTotal scanner detections, and OTX pulse counts. Because the HTTP and blocklist checks share a calendar date, that does not establish simultaneous measurement or direct comparability between them. The VirusTotal and OTX records also share a date, but each source applies its own method and scope. The chronology from first observation to the later checks shows only that these records were collected at different points in time.
Preserve the HTTP check record for ldglive3.com, the blocklist check record, and the VirusTotal and OTX records as separate artifacts. Compare the HTTP response record against later HTTP checks of ldglive3.com rather than against blocklist or scanner records. Review the external blocklist entries and the phishdestroy internal listing through their own source interfaces. Re-check the domain's HTTP response and blocklist status before relying on any single record.
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='ldglive3.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
love.ns.cloudflare.comLocation describes the IP network.
13 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