Analysis of the domain flack-allocation.online indicates it is an active generic phishing infrastructure registered on July 22, 2026, through Spaceship, Inc. The domain is currently flagged on two security blocklists, PhishDestroy and SEAL, suggesting detection by automated or community-driven threat intelligence systems. Infrastructure details reveal the domain resolves to the IP address 34.216.117.25, with nameservers configured as launch1.spaceship.net and launch2.spaceship.net, both associated with the registrar's hosting services.
No specific brand impersonation, phishing kit, or scam category has been identified in the available data, and the exact content or target of the site remains unconfirmed. Defenders should treat this domain as suspicious based on its presence on multiple blocklists and recent registration, which aligns with common phishing lifecycle patterns.
The domain's active status as of July 24, 2026, indicates ongoing risk, and network-level blocking or monitoring is recommended for organizations. Further investigation into the IP address and registrar history may provide additional context, though no evidence of prior malicious activity linked to this infrastructure is currently available in the provided data.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='flack-allocation.online', port=80): Max retries exceeded with url: / (Caused by NewConnect
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:12:29 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-07-27 22:28:07 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-27 22:28:07 UTC → 2026-09-30 16:14:55 UTC · 1,553.78hmidpoint estimate ≈ 2026-08-29 07:21:31 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.
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
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.
Domain Status Transition2026-08-05 22:00:35 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-07-24 09:19:22 UTC
VirusTotal scanner detections updated from None to 2. Added scanner alerts: Forcepoint ThreatSeeker, LevelBlue.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 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)
