VirusTotal
15 / 89
“app.lntredes.com”
On 2026-10-01, app.lntredes.com returned HTTP status 502 in a recorded check, and the domain was first observed on 2026-09-05. The publisher-owned PhishDestroy catalogue lists this domain, while the VirusTotal check on 2026-09-17 recorded 15 detections across 89 scanners.
The PhishDestroy internal listing records app.lntredes.com as listed in that publisher-owned catalogue. A VirusTotal check dated 2026-09-17 recorded 15 detections out of 89 scanners, with observation time known marked false. The HTTP check dated 2026-10-01 recorded status 502, and the first observation of the domain is dated 2026-09-05.
The PhishDestroy listing and the VirusTotal detection count are separate source records that describe different kinds of observation, so they should be read alongside each other rather than merged. The HTTP 502 response describes only the response recorded on that date and does not establish what the domain serves at other times. The gap between the first observation and the later checks shows the records span more than one calendar date, but the dates alone do not demonstrate a change in behavior.
Preserve the PhishDestroy listing record and the VirusTotal record for app.lntredes.com as separate source documents. Compare the HTTP response record with the first-observation record when reviewing the domain's timeline. Use the recorded HTTP status and the VirusTotal detection count as distinct inputs when deciding what further checks to run.
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='app.lntredes.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
quincy.ns.cloudflare.comLocation describes the IP network.
11 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