Analysis of dexrp.website indicates that the domain is being used for a crypto‑presale phishing campaign. The site was registered on March 02, 2026 through Hostinger Operations, UAB and is currently taken offline, returning no HTTP content. No TLS certificate is present, confirming that the service was delivered over plain HTTP. The page title observed before takedown was "Join the DeXRP Presale – Be Part of the Future of Decentralized Trading", which aligns with the declared crypto scam type.
Infrastructure traces show the domain resolving to IP address 46.202.182.149, hosted in the United States under AS47583 Hostinger International Limited. Nameservers are ns1.dns-parking.com and ns2.dns-parking.com, typical of parking services. Threat‑intel feeds have flagged the domain on four security blocklists, and it is actively blocked by PhishDestroy, MetaMask, ScamSniffer, and SEAL. VirusTotal analysis recorded three detections out of ninety‑three scanning engines, providing additional corroboration of malicious intent.
Evidence gaps include the lack of a current web payload, making it impossible to validate the exact phishing mechanics or any credential‑harvesting forms. Defenders should continue to block the domain at DNS and network layers, monitor for any resurrection of the host under new subdomains, and add the IP address to outbound‑traffic deny lists. Ongoing surveillance of Hostinger‑owned IP ranges for similar patterns is advised, as the registrar and hosting provider have been repeatedly leveraged for rapid phishing deployments.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='dexrp.website', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
DOM Analysisanalyzed 2026年7月29日score 63/1006 brand signals
Submitted URLhttp://dexrp.website/
案件 ID
ICANN OVERSIGHT
认证和 RAA 背景
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:09:23 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 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.
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.
14 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.
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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
(LT)
