The domain www.ascensum.io is currently active and classified as a high‑risk phishing site. Registration data shows the domain was created on December 04, 2025 through NAMECHEAP INC, and it is served by the authoritative nameservers dns1.registrar-servers.com and dns2.registrar-servers.com. DNS resolution points to the single IPv4 address 216.150.1.1.
Threat intelligence indicates that the domain appears on one public security blocklist and has been explicitly blocked by the PhishDestroy service. On VirusTotal, one out of ninety‑one scanned security vendors raised a detection flag for the domain, confirming that at least one vendor has identified malicious behavior. No additional public intelligence such as SSL certificate details, HTTP status codes, or page titles has been released, leaving the exact content and payload of the site unverified.
Analysts should assume the domain is being used for credential‑harvesting or other phishing tactics given its classification and the limited detection evidence. Defensive actions include adding www.ascensum.io to network blocklists, restricting outbound connections to its IP address 216.150.1.1, and monitoring DNS queries for the associated nameservers. Continuous re‑evaluation is advised, as further detections or changes in hosting infrastructure could increase the threat posture.
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.
IoC Extractionscanned 2026年8月4日2 wallet · 1 Telegram IoCs
Submitted URLhttps://www.ascensum.io/
Favicon Hash
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(US)
