The domain maglckeden.online is a generic phishing site designed to deceive users into disclosing sensitive information such as login credentials or personal data. It does not impersonate a specific brand and has no known association with a crypto drainer kit. As of the latest verification, maglckeden.online has been taken offline, though it remains under investigation for its prior activity.
Technical indicators show that maglckeden.online was registered through HOSTINGER operations, UAB on August 09, 2024, and resolved to the IP address 198.18.0.206. The domain was detected by 0 of 95 VirusTotal vendors and appeared on 2 security blocklists, specifically PhishDestroy and Enkrypt. No SSL certificate was issued, and the page title observed was 'maglckeden.online'. The domain was also found in 1 AlienVault OTX threat intelligence pulse, with a Gridinsoft trust score of 0 out of 100. Nameservers associated with the domain were ns1.dns-expired.com and ns2.dns-expired.com.
Users who may have interacted with maglckeden.online should immediately change any passwords or credentials entered on the site, enable two-factor authentication (2FA) on all accounts, and monitor for signs of fraud or unauthorized access. If financial or cryptocurrency-related information was disclosed, consider revoking token approvals and transferring funds to a new wallet. To report the phishing domain, submit it to platforms such as Google Safe Browsing, PhishTank, or the Anti-Phishing Working Group (APWG). Additionally, victims can file a complaint with their local cybercrime unit or the Internet Crime Complaint Center (IC3).
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='maglckeden.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
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.
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:10:13 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-16 22:13:40 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-16 22:13:40 UTC → 2026-09-30 16:14:55 UTC · 2,538.02hmidpoint estimate ≈ 2026-08-08 19:14:17 UTC · precision very low · basis bounded
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.
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.
黑名单检测
见于 1 blocklist: Enkrypt
2026年10月14日
OTX Community References
1 community publication reference on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年3月2日
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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.
(LT)
