PhishDestroy first recorded invictus-meets-infinity.global on 2026-07-10. Stored VirusTotal result: 15/92 engines flagged. Malicious: 13. Suspicious: 2. Analysis time (as stored): 2026-09-30 09:06 UTC. Retrieved (as stored): 2026-10-28 09:49 UTC. Listed by external blocklists: MetaMask, SEAL.
Page title: “invictus-meets-infinity.global - This website is for sale! - invictus meets infinity Resources and Information.”
More about the sources
Recorded security signals
Stored VirusTotal result: 15/92 engines flagged. Malicious: 13. Suspicious: 2. Analysis time (as stored): 2026-09-30 09:06 UTC. Retrieved (as stored): 2026-10-28 09:49 UTC. Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@ionos.com. The latest stored availability evidence still shows the domain reachable; 4 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Elapsed since first report
4 months
Reports sent
1
Latest case ID
PD-20260712-BBFEB4
Current status
HTTP 301 at latest stored check
Analysis
Domain summary
PhishDestroy first recorded invictus-meets-infinity.global on 2026-07-10. Stored VirusTotal result: 15/92 engines flagged. Malicious: 13. Suspicious: 2. Analysis time (as stored): 2026-09-30 09:06 UTC. Retrieved (as stored): 2026-10-28 09:49 UTC. Listed by external blocklists: MetaMask, SEAL. Risk: critical (evidence score 100/100). Registrar: IONOS SE. Status: Last known active. Hosting: IONOS SE. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
The domain invictus-meets-infinity.global is currently flagged for generic phishing activities. A thorough analysis indicates that this domain is likely associated with attempts to deceive users via methods such as brand impersonation or fake login attempts. Examination of the infrastructure does not yet reveal specific phishing kits or drainer mechanisms, but its current profile suggests potential threats to user credentials and financial information.
Technical evaluation yields precise metrics: the VirusTotal score stands at 0/95, indicating that no detections have been made, which may imply the domain is currently unrecognized by automated threat detection systems. The domain was registered through IONOS SE, with an IP resolution to 217.160.0.225. Notably, the domain was created on July 02, 2026, indicating a recent establishment which may factor into its high-risk categorization. Moreover, no information is currently present in any standard Google Safe Browsing (GSB) databases, which further complicates the identification of threats associated with this domain.
The current status of invictus-meets-infinity.global remains active and under investigation, indicating the necessity for continued monitoring. Recommended response actions include heightened scrutiny of user interactions and reporting the domain to relevant cyber threat intelligence platforms. The existing risk to users should not be underestimated, as active domains can become rapidly operational for phishing campaigns. Users are advised to exercise caution, refrain from inputting sensitive information, and verify any requests for login credentials or personal data.
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.
The domain invictus-meets-infinity.global is currently flagged for generic phishing activities. A thorough analysis indicates that this domain is likely associated with attempts to deceive users via methods such as brand impersonation or fake login attempts. Examination of the infrastructure does not yet reveal specific phishing kits or drainer mechanisms, but its current profile suggests potential threats to user credentials and financial information. Technical evaluation yields precise metrics: the VirusTotal score stands at 0/95, indicating that no detections have been made, which may imply the domain is currently unrecognized by automated threat detection systems. The domain was registered through IONOS SE, with an IP resolution to 217.160.0.225. Notably, the domain was created on July 02, 2026, indicating a recent establishment which may factor into its high-risk categorization. Moreover, no information is currently present in any standard Google Safe Browsing (GSB) databases, which further complicates the identification of threats associated with this domain. The current status of invictus-meets-infinity.global remains active and under investigation, indicating the necessity for continued monitoring. Recommended response actions include heightened scrutiny of user interactions and reporting the domain to relevant cyber threat intelligence platforms. The existing risk to users should not be underestimated, as active domains can become rapidly operational for phishing campaigns. Users are advised to exercise caution, refrain from inputting sensitive information, and verify any requests for login credentials or personal data.
PhishDestroy rates invictus-meets-infinity.global as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-07-10. Stored VirusTotal result: 15/92 engines flagged. Malicious: 13. Suspicious: 2. Analysis time (as stored): 2026-09-30 09:06 UTC. Retrieved (as stored): 2026-10-28 09:49 UTC. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is invictus-meets-infinity.global safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on invictus-meets-infinity.global. A confirmed blockchain transaction cannot be reversed.
What should I do if I used invictus-meets-infinity.global?
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.
IP Reputation217.160.0.2253/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worseThis IP address has a low abuse score, but the domain itself is recognized as phishing.39 reportsHackingWeb App Attackchecked 2026-11-13last reported
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
Resolved IP
217.160.0.225
Network ASN
AS8560
AS name
IONOS-AS IONOS SE, DE
Organization
IONOS SE
Observed location
Frankfurt am Main, DE
Server header
Apache
Nameservers 4
ns1037.ui-dns.org
ns1047.ui-dns.com
ns1057.ui-dns.de
ns1121.ui-dns.biz
Mail routing 1 MX record
mail-gateway.domcollect.compriority 10
Location describes the IP network.
TLS certificate
Issuer
DigiCert Inc / Encryption Everywhere DV TLS CA - G2
Valid from
2026-07-28 00:00:00
Valid until
2026-10-25 23:59:59
Hostname match
Yes
Validity
Stored certificate expired
Collection time
2026-07-30 01:02 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta0e4b488235f1e6fa93203996d6af20a7de29438dd27e7e2c64cf3ee855fa473Certificate names · 1 SAN
invictus-meets-infinity.global
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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 03:39 UTC.
Recorded events: 12. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
6 entries
Lifecycle
Domain registered
Added to PhishDestroy+7 d 13 h
First abuse report sent+55 h 26 min
VirusTotal analysis with detections+79 d 13 h
Reported 9 d 20 h after registration
AlienVault OTX
5 community references
+43 d 20 h
VirusTotal
15/92 engine detections
+79 d 13 h
ionos.com
Acknowledged the report
same minute
Abuse report sent
PD-20260712-BBFEB4 · Receipt 51719
abuse@ionos.com
+55 h 26 min
Added to PhishDestroy
invictus-meets-infinity.global
same minute
URLScan
Page captured
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 matches5
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 invictus-meets-infinity.global)
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.