This domain, allegro-supply.org, is engineered to mimic legitimate retail checkout portals, specifically targeting users of a well-known e-commerce platform. Analysis indicates the site presents fraudulent payment forms designed to harvest credit card details, billing addresses, and login credentials under the guise of completing a purchase. The threat extends beyond credential theft, as victims may also be prompted to download malicious browser extensions or executables disguised as order confirmations, potentially leading to persistent account compromise or malware installation. Infrastructure analysis reveals the domain was registered on February 24, 2026, through NameSilo, a registrar frequently observed in phishing campaigns due to its low-cost and privacy-protection services. The domain resolves to the IP address 172.67.186.234, hosted on Cloudflare’s network (AS13335), which provides SSL encryption (certificate E7) to lend an appearance of legitimacy. Detection metrics from VirusTotal show 22 out of 95 security vendors flagging the domain as malicious, while it appears on one security blocklist, indicating moderate but growing awareness within the threat intelligence community. Users who interacted with allegro-supply.org should immediately revoke any entered credentials, particularly those associated with financial accounts or the impersonated retail platform. It is recommended to conduct a full antivirus scan using updated signatures to detect potential secondary infections. Financial institutions should be notified to monitor for unauthorized transactions, and affected devices should be isolated from sensitive networks until verified clean. Organizations should update internal blocklists to include this domain and its resolving IP to prevent further exposure.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='allegro-supply.org', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
DOM Analysisanalyzed 2026年7月29日score 78/1001 brand signal
Impersonates
Genericcloudflare
TLS 证书
Hostname coverage not recorded·
颁发者 E7
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.67.186.234
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Edge-IP 声誉不属于此域。
Location describes the IP network.
TLS 证书
Issuer
E7
Valid from
2026-02-20 10:40:54
Valid until
2026-05-20 10:40:54
Hostname coverage
Hostname coverage not recorded
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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:54 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-03-17 11:03:46 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-03-17 11:03:46 UTC → 2026-09-30 16:14:55 UTC · 4,733.19hmidpoint estimate ≈ 2026-06-24 01:39:20 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.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
