Security engines reporting a detection: 6. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 72H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 5 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
The domain sdl.link was recorded on 2026-10-08 with several security sources noting its presence, including a VirusTotal scan and listings on two external blocklists. On the same date, sdl.link was also internally listed by Phishdestroy, providing another source observation.
Recorded Evidence
On 2026-10-08, VirusTotal reported 6 detections out of 92 scanners for sdl.link. The domain appeared on the MetaMask and SEAL external blocklists as of that date. OTX referenced sdl.link in 2 pulses on 2026-10-08. Phishdestroy internally listed the domain, and its registrar was NAMECHEAP INC with a registration date of 2024-03-14.
Interpretation
The available records show that sdl.link was cited by multiple security sources on the same date, each providing a distinct observation. These include detection counts from VirusTotal, appearances on two named blocklists, and references in OTX pulses, as well as an internal listing by Phishdestroy. Each of these records offers a different perspective on how the domain has been tracked or categorized by various monitoring platforms.
Recommended Actions
For sdl.link, it is advisable to preserve the VirusTotal scan results, external blocklist entries, and OTX pulse references for ongoing review. Comparing these records over time may help identify changes in how the domain is classified by different security sources. Retaining the internal listing from Phishdestroy can also support further analysis or investigation.
Extracted from stored page analysis
Observed indicators
2 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
RegistrationCreated Mar 14, 2024 —Expires Mar 14, 2027
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedOct 8, 2026
DOM Analysisanalyzed Oct 9, 2026score 90/10011 brand signals
IoC Extractionscanned Oct 9, 20262 wallet · 1 Telegram IoCs
Submitted URLhttp://sdl.link/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
162.255.119.188
Network ASN
AS22612
Organization
Web-hosting.com
Observed location
Los Angeles, US
Server header
nginx/1.31.6
Nameservers 2
dns1.registrar-servers.com
dns2.registrar-servers.com
Mail routing 5 MX records
eforward2.registrar-servers.compriority 10
eforward3.registrar-servers.compriority 10
eforward1.registrar-servers.compriority 10
eforward4.registrar-servers.compriority 15
eforward5.registrar-servers.compriority 20
Location describes the IP network.
TLS certificate
Issuer
Amazon RSA 2048 M01
Hostname coverage
Hostname coverage not recorded
Collection time
2026-10-14 01:02:27 UTC
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 22:05:34 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 22:29:33 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Last analyzed Previous stored snapshot: 6 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
URLQuery
VIPRE
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-08 14:51:12 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 162.255.119.188.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
6 evidence signal groups linked1 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · sdl.link
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(IS)
