VirusTotal
6 / 90 engine detections
打开报告“aerodrome.network | 522: Connection timed out”
冒充 Aerodrome: aerodrome.network — 未验证. 证据摘要: VirusTotal 6/90 (alphaMountain.ai, Chong Lua Dao, Emsisoft, Forcepoint ThreatSeeker, Gridinsoft); 3 external…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 90 engine detections
打开报告23 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain aerodrome.network was registered on 21 February 2026 through Tucows Domains Inc. It resolves to the Cloudflare‑owned address 188.114.97.3 (AS13335, United States) and is served by the nameservers peyton.ns.cloudflare.com and frida.ns.cloudflare.com. The site is protected by Cloudflare with HTTP/3 enabled and presents an SSL certificate issued by Google Trust Services / WE1. HTTP requests return a 403 status and the only observable page title is "aerodrome.network | 522: Connection timed out". Gridinsoft assigns the domain a trust score of 0 / 100. The domain appears on four public blocklists and is actively blocked by PhishDestroy, Polkadot, Enkrypt and Codeesura. VirusTotal analysis shows that 2 of 93 security vendors flagged the domain as malicious. The threat is classified as brand impersonation targeting the Aerodrome brand, with the scam type recorded as impersonation. Current intelligence indicates the infrastructure remains active as of 12 July 2026. Defenders should add aerodrome.network to deny‑list rules, monitor DNS queries for the 188.114.97.3 address, and enforce blocklist updates to ensure traffic is blocked at network perimeter. Continuous observation is recommended to detect any change in response codes or additional malicious payloads.
Last checked
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.
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.
Edge-IP 声誉不属于此域。
frida.ns.cloudflare.comLocation describes the IP network.
7cff06d13e6ff386928b5e7855dbbe4a952af5e57f5412f2a2fc682256984a12Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
status_split · unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='aerodrome.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
aerodrome.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
redirected→dns_inactive
dns_nxdomain
未知→redirected
http_redirect
不可用→可访问
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
可访问→不可用
https://radar.cloudflare.com/scan/7a2b1682-33db-4598-9785-30aac1723819
可访问→不可用
23 community references
View sourceNo threat flag
View source6/90 engine detections
View sourcePage captured
View sourceaerodrome.network
View source1 条社区报告
类别PHISHING
Automated report created by SEAL
由 1 名社区成员报告;首次发现于 2025年8月7日
Listed domains receive at least one abuse report; this entry has no retained notification history.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
aerodrome.network)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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.