VirusTotal
6 / 91
Interpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“KRAKEN”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
6 / 91
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
3 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
On 2026-10-01, slon14.as returned an HTTP status of 200 in the recorded HTTP check. The domain also appears in the publisher-owned PhishDestroy catalogue, a listing recorded separately from the scanner results.
The HTTP check on 2026-10-01 recorded status 200 for slon14.as. VirusTotal, checked on 2026-09-29, reported 6 detections across 91 scanners. OTX, checked on 2026-09-19, showed 3 pulses. The domain was first observed on 2026-09-17, the same date as a PageSpeed performance score of 100. Registration occurred on 2026-08-28 with registrar Dynadot Inc., and the SSL scan on 2026-09-18 identified Let's Encrypt / YE1 as issuer.
The VirusTotal detections and OTX pulses are separate source observations with different dates, so they should be read as independent records rather than combined into a single trend. The HTTP 200 response describes only the recorded response on its check date and does not establish what content the domain serves. The PhishDestroy listing is a publisher-owned catalogue entry, and its presence alongside scanner detections gives a reader multiple dated records to compare without implying a verdict.
Preserve the PhishDestroy catalogue entry, the VirusTotal result, and the OTX pulses for slon14.as as separate records. Compare the HTTP response record with the PageSpeed observation to see whether both describe the same reachable state. Review the VirusTotal detections and OTX pulses independently, since each source uses its own methodology. Keep the first-observed date and the SSL scan record available for later comparison against new observations of slon14.as.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='slon14.as', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<SOC
pns64.cloudns.ukLocation describes the IP network.
fa6db24be4579dc55e1b3581cdebb0e495413a07caecb28735e437d81a856905Saved 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 slon14.as · checked Sep 17, 2026
146.103.40.42.15 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.
114 stored lookalike domains
Showing 100 of 114
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