Analysis of the domain migayahome.digital indicates that it was active as a generic phishing infrastructure before being taken offline as of the report date, July 25, 2026. The domain is registered through Cloudflare, Inc. and resolves to the IP address 104.21.69.231, which belongs to the Cloudflare network (AS13335) located in the United States. Nameserver records point to abby.ns.cloudflare.com and seth.ns.cloudflare.com, confirming reliance on Cloudflare DNS services. No SSL certificate is associated with the domain, suggesting that any web service would have been delivered over plain HTTP.
Reputation data shows a Gridinsoft trust score of 0 out of 100, and the domain is listed on a single security blocklist. It has been blocked by the PhishDestroy remediation service. Threat intelligence aggregators have recorded the domain in fifteen AlienVault OTX pulses, and VirusTotal reports that sixteen of ninety-five scanned security vendors flagged the domain as malicious. The elevated risk rating aligns with these observations.
Uncertainty remains regarding the specific phishing lure employed, as no page title or content analysis is available. Defenders should continue to block the domain at network perimeter devices, update DNS filtering to include the associated IP and nameservers, and monitor for any re‑registration attempts. Additional scrutiny of any future domains using the same Cloudflare account or similar IP ranges is recommended to pre‑empt potential re‑use of this infrastructure.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='migayahome.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
DOM Analysisanalyzed 2026年4月29日score 83/1001 brand signal
Submitted URLhttp://migayahome.digital/
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.
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:33 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-05-22 08:12:34 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-22 08:12:34 UTC → 2026-09-30 16:14:55 UTC · 3,152.04hmidpoint estimate ≈ 2026-07-27 00:13:44 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.
13 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.
(US)
