PhishDestroy first recorded fifa.black on 2026-06-01. Stored VirusTotal result: 14/92 engines flagged. malicious: 13. suspicious: 1. Analysis time (as stored): 2026-10-26 09:45 UTC. Retrieved (as stored): 2026-10-31 06:11 UTC.
Page title: “FIFA World Cup 2026™ Tickets | Host Cities, Dates, Teams, Tickets”
More about the sources
Recorded security signals
Stored VirusTotal result: 14/92 engines flagged. malicious: 13. suspicious: 1. Analysis time (as stored): 2026-10-26 09:45 UTC. Retrieved (as stored): 2026-10-31 06:11 UTC. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded fifa.black on 2026-06-01. Stored VirusTotal result: 14/92 engines flagged. malicious: 13. suspicious: 1. Analysis time (as stored): 2026-10-26 09:45 UTC. Retrieved (as stored): 2026-10-31 06:11 UTC. Risk: critical (evidence score 100/100). Registrar: Alibaba Cloud Computing. Status: Content unavailable. Hosting: CLOUDFLARENET - Cloudflare, Inc., US. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
Domain fifa.black is assessed as a generic_phishing infrastructure engaging in brand impersonation of FIFA-related ticketing services, specifically mimicking FIFA World Cup 2026™ ticket distribution pages. The observed page title indicates fraudulent promotion of tickets, host cities, and event scheduling content designed to capture user credentials or payment data.
Technical intelligence shows the domain was flagged by 19 of 95 VirusTotal security vendors. It was registered through Alibaba Cloud Computing Ltd. d/b/a HiChina (net.cn). The domain resolves to IP 188.114.96.3 and is hosted within US infrastructure under AS13335 Cloudflare, Inc. The domain was created on November 17, 2025. It has no SSL certificate observed at time of analysis, appears on 1 security blocklist, and has been blocked by PhishDestroy. Google Safe Browsing status is not explicitly listed in provided data.
The domain is currently offline, indicating takedown or suspension, but historical indicators confirm active phishing intent targeting FIFA brand users. Absence of TLS configuration and high-confidence brand impersonation increase credential theft risk. Despite inactivity, residual exposure remains through cached links or mirrored infrastructure. Recommended actions include blocking IP 188.114.96.3, monitoring for related Cloudflare-hosted phishing clusters, and advising users to avoid any FIFA ticket-related login prompts originating outside official domains.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Open report Page code check by a separate monitor · 0 / 100 · 2026-06-11T02:20:12Z
This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Heuristic score
0
Analyzed at
2026-06-11T02:20:12Z
Source timestamp
2026-06-11 04:20:12
Technical metadata
PhishDestroy narrative
Narrative generation metadata
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Ai title
fifa.black Fake FIFA Ticket Scam Alert
Ai description
fifa.black is a brand impersonation credential theft domain targeting FIFA ticket users; 19/95 vendors flagged malicious infrastructure activity.
Ai summary
Domain fifa.black is assessed as a generic_phishing infrastructure engaging in brand impersonation of FIFA-related ticketing services, specifically mimicking FIFA World Cup 2026™ ticket distribution pages. The observed page title indicates fraudulent promotion of tickets, host cities, and event scheduling content designed to capture user credentials or payment data. Technical intelligence shows the domain was flagged by 19 of 95 VirusTotal security vendors. It was registered through Alibaba Cloud Computing Ltd. d/b/a HiChina (net.cn). The domain resolves to IP 188.114.96.3 and is hosted within US infrastructure under AS13335 Cloudflare, Inc. The domain was created on November 17, 2025. It has no SSL certificate observed at time of analysis, appears on 1 security blocklist, and has been blocked by PhishDestroy. Google Safe Browsing status is not explicitly listed in provided data. The domain is currently offline, indicating takedown or suspension, but historical indicators confirm active phishing intent targeting FIFA brand users. Absence of TLS configuration and high-confidence brand impersonation increase credential theft risk. Despite inactivity, residual exposure remains through cached links or mirrored infrastructure. Recommended actions include blocking IP 188.114.96.3, monitoring for related Cloudflare-hosted phishing clusters, and advising users to avoid any FIFA ticket-related login prompts originating outside official domains.
PhishDestroy rates fifa.black as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-06-01. Stored VirusTotal result: 14/92 engines flagged. malicious: 13. suspicious: 1. Analysis time (as stored): 2026-10-26 09:45 UTC. Retrieved (as stored): 2026-10-31 06:11 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is fifa.black safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on fifa.black. A confirmed blockchain transaction cannot be reversed.
What should I do if I used fifa.black?
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First Detected2026-06-01
DOM Analysisanalyzed 2026-06-11score 83/1001 brand signal
Submitted URLhttp://fifa.black/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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.
Accountability draft Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
izabella.ns.cloudflare.com
justin.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-05-25 14:50:57
Valid until
2026-08-23 14:50:56
Hostname match
Yes
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprintfb4116d16ce987bd1bdd73c0b464d2981e70e6b181f4a655c310368a97b78624Certificate names · 2 SANs
*.fifa.black
fifa.black
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAIN
RDAP registration
Observed timelinelast reachable: 2026-07-02 10:04 UTCcurrent episode first observed: 2026-09-30 16:14 UTCobserved RIP window: 2026-07-02 10:04 UTC → 2026-09-30 16:14 UTC · 2,166.18hmidpoint estimate ≈ 2026-08-16 13:09 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.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 04:07 UTC.
Recorded events: 14. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Time to First Unavailability
Hours from detection to the first unavailable observation: 1815
Recorded activity
5 entries
Lifecycle
Domain registered
First abuse report sent+196 d 4 h
Added to PhishDestroy+56 min
VirusTotal analysis with detections+146 d 12 h
Reported 196 d 4 h after registration
VirusTotal
14/92 engine detections
+146 d 10 h
AlienVault OTX
4 community references
+1 h 34 min
Added to PhishDestroy
fifa.black
+56 min
Abuse report sent
PD-20260601-F6DCA7 · Receipt 42994
domainabuse@service.aliyun.com
+4 min
URLScan
Malicious
How we investigate & report
Public scans, evidence and abuse channels
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.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches4
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including fifa.black)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
About this reportSources, observation dates and corrections
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.