Analysis indicates that the domain 2026fifaworldcuptickets.online was registered on June 12, 2026 through HOSTINGER operations, UAB. The domain resolves to the IPv6 address 2a02:4780:84:a40e:8e4:658e:66bf:94fe, which is currently listed on a single security blocklist and is actively blocked by PhishDestroy. VirusTotal scans show that 16 of 91 security vendors have flagged the domain, reflecting a modest but notable detection rate.
The threat classification is generic phishing with an elevated risk rating, and the campaign remains active according to the latest intelligence. No public information about the site’s page title, SSL certificate, or HTTP response has been disclosed, limiting precise assessment of the phishing lure or the credential‑harvesting mechanism employed. The presence of the domain on a blocklist and multi‑vendor detections suggests that the infrastructure is being used for malicious credential collection, although the exact content and targeted brand remain uncertain.
Defenders should add the domain and its resolving IPv6 address to local deny lists, monitor DNS queries for related lookups, and ensure endpoint protection solutions are updated to reflect the 16 vendor detections. Organizations are advised to educate users about unsolicited communications referencing World Cup tickets, enforce multi‑factor authentication, and monitor for anomalous login attempts that may stem from this infrastructure. Continuous re‑evaluation is recommended as additional indicators such as page titles, SSL details, or further blocklist listings may emerge.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='2026fifaworldcuptickets.online', port=80): Max retries exceeded with url: / (Caused by New
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.
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:12:49 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 UTC
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.
Domain Status Transition2026-08-05 22:52:22 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-07-29 05:30:45 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 2a02:4780:84:a40e:8e4:658e:66bf:94fe.
VirusTotal Detections Update2026-06-25 21:27:21 UTC
VirusTotal scanner detections updated from 17 to 18. Added scanner alerts: ESET.
威胁响应 Pipeline
发现
Analysis
Monitoring
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.
(LT)
