Skip to security report
solidmaxgo.net favicon
Domain security and threat intelligence

solidmaxgo.net

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

This site displays a Russian-language gift ring promotion that requests phone numbers and verification codes to claim a virtual reward, while Spamhaus DBL lists it as spam, 7 of 92 engines on VirusTotal flagged it, and Cloudflare Radar rated it suspicious (Security Risks). If you interacted with it, secure your account immediately and revoke unauthorized sessions.

Page title: “ВАМ ПОДАРИЛИ КОЛЕЧКО 💍”

More about the sources
Recorded security signals

Use caution — do not enter credentials or personal information.

Spamhaus DBL: spam domain
Registrar
VietnamCNOBIN INFORMATION TEC…
Resolved IP
Canada172.67.183.203Cloudflare, Inc. · CDN
First seen by PhishDestroy
2026-11-12
Page captures
open gallery
Reports sent
view timeline
2026-11-12 1 Report Sent CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded solidmaxgo.net on 2026-11-12. Risk: critical (evidence score 76/100). Registrar: CNOBIN INFORMATION TEC…. Status: Content unavailable. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Content unavailable
Hosting
Canada172.67.183.203Cloudflare, Inc. · CDN
Registrar
VietnamCNOBIN INFORMATION TEC…
Page captures
7

URLScan capture · 2026-11-12 22:15 UTC · SHA-256 11efaa03…80b6755

PhishDestroy analysis, reviewed version

Gift ring promotion and phone verification setup

The page displays a dark-themed card centered around a virtual ring graphic with the Russian headline "ВАМ ПОДАРИЛИ КОЛЕЧКО 💍" and the prompt "Жми кнопку что забрать подарок 👇". Above the main heading, a smaller box shows an image of a ring with the text "Сохранённый подарок" and "Display this gift on your page.", accompanied by a blue button labeled "Посмотреть". Below the main text sits a bright green button reading "ЗАБРАТЬ ПОДАРОК". At the bottom, a small notice inside a bordered box states "Мы попросим номер и код, для того чтобы вы получили подарок 1 раз". The interface is designed to capture authentication credentials through phone verification under the guise of delivering a virtual item.

Domain age and security telemetry findings

It was registered on 12 Nov 2026 and reported the same day. Furthermore, it sits behind Cloudflare, which hides the real server, making it harder to trace the operators behind the campaign. Spamhaus DBL lists it as spam, 7 of 92 engines on VirusTotal flagged it, and Cloudflare Radar rated it suspicious (Security Risks), including Fortinet, Forcepoint ThreatSeeker and CRDF.

Risks of claim verification pages

Pages requesting phone numbers and confirmation codes under the promise of a digital gift typically lead to account takeover attempts on messaging platforms. Entering verification codes can grant external parties full access to personal accounts, allowing attackers to propagate similar links to contacts or misuse personal information.

Source evidence 5 sources

Gridinsoft

1/100

Spamhaus DBL

spam domain

URLScan

Page capture

SHA-256 304e7b84…4475146

Open report
URLScanOriginal source recordObserved: 20 fields
Separate monitor record

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a1d160-fa56-7653-9388-840ca3ed9d6f
Enriched at
2026-11-14T09:13:53Z
Source timestamps
Urlscan enriched at: 2026-11-14 10:13:53
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
solidmaxgo.net — Russian Telegram gift ring phishing
AI description
solidmaxgo.net mimics a virtual gift claim page, flagged by Spamhaus DBL and 7 VirusTotal engines. Protect your account from session access.
AI summary
Gift ring promotion and phone verification setup The page displays a dark-themed card centered around a virtual ring graphic with the Russian headline "ВАМ ПОДАРИЛИ КОЛЕЧКО 💍" and the prompt "Жми кнопку что забрать подарок 👇". Above the main heading, a smaller box shows an image of a ring with the text "Сохранённый подарок" and "Display this gift on your page.", accompanied by a blue button labeled "Посмотреть". Below the main text sits a bright green button reading "ЗАБРАТЬ ПОДАРОК". At the bottom, a small notice inside a bordered box states "Мы попросим номер и код, для того чтобы вы получили подарок 1 раз". The interface is designed to capture authentication credentials through phone verification under the guise of delivering a virtual item. Domain age and security telemetry findings It was registered on 12 Nov 2026 and reported the same day. Furthermore, it sits behind Cloudflare, which hides the real server, making it harder to trace the operators behind the campaign. Spamhaus DBL lists it as spam, 7 of 92 engines on VirusTotal flagged it, and Cloudflare Radar rated it suspicious (Security Risks), including Fortinet, Forcepoint ThreatSeeker and CRDF. Risks of claim verification pages Pages requesting phone numbers and confirmation codes under the promise of a digital gift typically lead to account takeover attempts on messaging platforms. Entering verification codes can grant external parties full access to personal accounts, allowing attackers to propagate similar links to contacts or misuse personal information.
AI generated by
threat-v10-gemini
AI generated at
2026-11-20T13:28:08Z
Revision
68442f67c1c2518c071b0153f6f1b894f3c9f34316c625d08eabb361d78ef4af
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
VirusTotalOriginal source recordObserved: 13 fields
Open complete records
Website checksOriginal source recordRetrieved: 16 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

DNS servers

Nameservers
  • IP address
    172.64.35.134
    Host
    hasslo.ns.cloudflare.com
  • IP address
    173.245.58.218
    Host
    robin.ns.cloudflare.com
DNS zone
solidmaxgo.net

Location

IP address
2606:4700:3035::ac43:b7cb
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
solidmaxgo.net

DNS records

A
  • 104.21.48.101
  • 172.67.183.203
NS
  • hasslo.ns.cloudflare.com
  • robin.ns.cloudflare.com
SOA
Primary nameserver
hasslo.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2419958239
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3030::6815:3065
  • 2606:4700:3035::ac43:b7cb

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:3035::ac43:b7cb
IP version
6

Technology stack

Technologies
  • lit-html
  • lit-element
  • Cloudflare
  • HTTP/3

Registration record

Registrar
CNOBIN INFORMATION TECHNOLOGY LIMITED
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • hasslo.ns.cloudflare.com
  • robin.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
DNS server
NS: (IP: 172.64.35.134; Host: hasslo.ns.cloudflare.com), (IP: 173.245.58.218; Host: robin.ns.cloudflare.com); Zone: solidmaxgo.net
Location
IP: 2606:4700:3035::ac43:b7cb; ASN: 13335; Org: Cloudflare, Inc.; City: Toronto; Country: CA
SSL
Issuer: Let's Encrypt / YE1; Subject: solidmaxgo.net
DNS records
A: 104.21.48.101, 172.67.183.203; NS: hasslo.ns.cloudflare.com, robin.ns.cloudflare.com; Soa: Nsname: hasslo.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2419958239; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:3030::6815:3065, 2606:4700:3035::ac43:b7cb
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2606:4700:3035::ac43:b7cb; Family: 6
Tech stack
Technologies: lit-html, lit-element, Cloudflare, HTTP/3
Registration record
Registrar: CNOBIN INFORMATION TECHNOLOGY LIMITED; Created: 2026-11-12T08:27:20Z; Updated: 2026-11-12T08:27:20Z; Expires: 2027-11-12T08:27:20Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: hasslo.ns.cloudflare.com, robin.ns.cloudflare.com
HTTP headers
Headers: Server: cloudflare

Questions about solidmaxgo.net

Is solidmaxgo.net legit?

No, solidmaxgo.net is not a legitimate service. Spamhaus DBL lists it as spam, 7 of 92 engines on VirusTotal flagged it, and Cloudflare Radar rated it suspicious (Security Risks), proving it is part of an active malicious network.

What happens if I entered my phone number and code?

Entering a verification code likely allowed attackers to log into your messaging or social account. You should immediately check active sessions in your account settings and log out any unfamiliar devices.

Why does the page show a ring gift?

The virtual ring graphic and phrases like "ВАМ ПОДАРИЛИ КОЛЕЧКО 💍" are social engineering lures designed to appeal to users receiving unexpected rewards. These incentives encourage visitors to bypass normal caution and complete the verification steps.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (7)

All capture links and hashes (7)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 85 report ↗
IP Context Canada172.67.183.203 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar CNOBIN INFORMATION TEC… VN(VN)
RegistrationExpires 2027-11-12
Time to First Unavailability 3 days
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.
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-12
DOM Analysisanalyzed 2026-11-13score 0/100
Submitted URLhttps://solidmaxgo.net/w/iwiXJizys
Case ID
Observed page title
ВАМ ПОДАРИЛИ КОЛЕЧКО 💍
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 79 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.67.183.203
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • hasslo.ns.cloudflare.com
  • robin.ns.cloudflare.com

SOA

  • nsname: hasslo.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2419958239
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-11-12 07:31:56
Valid until
2027-02-10 07:31:55
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintad63e58ad70fdbd12711512d21d4b0ddc2deaa1ed180053fd3d358a7e72fd342
Certificate names · 2 SANs
  • *.solidmaxgo.net
  • solidmaxgo.net

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-11-21 18:03 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN
RDAP registration
Observed timeline last reachable: 2026-11-14 11:07 UTC current episode first observed: 2026-11-16 17:12 UTC observed RIP window: 2026-11-14 11:07 UTC → 2026-11-16 17:12 UTC · 54.09h midpoint estimate ≈ 2026-11-15 14:09 UTC · precision 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.
Technologies · 2 identified
Open complete records
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://solidmaxgo.net/w/iwiXJizys
ВАМ ПОДАРИЛИ КОЛЕЧКО 💍
Response
HTTP 200
HTML body
11.3 KB
Compressed
4.1 KB
Links
0 internal · 0 external
Detected technologies
cloudflarereact
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: e7916b397714f7b72120cc48a568a15e16862707257f2954babd87c8a91ec36e
Saved response-header values · 12
Alt-Svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a598e109ce1cfba5-AMS
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Thu, 12 Nov 2026 22:12:35 GMT
NEL
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=2OYjUVrKcuQ1IDJuWUN7vltvFsFtaYBSSK6w23An9zowhrL2ggRiFdv%2BknutPMnwXaxEmkqEoTigb%2BZaelmfU8G6rs5bwzgf0fqgV%2FmW9UwSK7f8zJ7rggLmO2RF1LCrMw%3D%3D"
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked

Values retained by the collector; long values may be shortened during collection.

Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
54.09
Estimate basis
Bounded by observations
Estimate precision
Low

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data109
Open complete records

Captured network requests

Network requests: 26 SHA-256 hashes: 26 URLScan scan:

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-11-12 22:22 UTC.

Open this scan on URLScan 01a1d1d8-3406-70f8-be8d-6630273a984f ↗

Stored observation history3

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Not resolving in DNS

    domain does not exist in DNS

  2. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  3. Domain monitor · First collection record

    Reachable

All retained availability observations16
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · recorded

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    solidmaxgo.net detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: CNOBIN INFORMATION TECHNOLOGY LIMITED. Abuse contacts: 1.
    • abuse@ordertld.com
Publication & AvailabilityDestroyList Published · Content Observed Unavailable · Time to First Unavailability recorded
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Content Observed Unavailable
    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: 63

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+13 h 44 min
  3. First abuse report sent+11 min

Reported 13 h 56 min after registration

  1. OrderTLD

    Replied to the report

    +9 h 3 min
  2. Abuse report sent

    PD-B7BB238024B6C6599AE5 · Receipt 84827

    abuse@ordertld.com
    +2 min
  3. URLScan

    Page captured

    +9 min
  4. Added to PhishDestroy

    solidmaxgo.net

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

solidmaxgo.net

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-B7BB238024B6C6599AE5 Recipient: abuse@ordertld.com
Page title stored with report: ВАМ ПОДАРИЛИ КОЛЕЧКО 💍
PDF notice generated
Deep Analysis

Were You Affected by This Site?

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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

After a phishing incident

Recommendations & Advice for Victims

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 solidmaxgo.net)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/solidmaxgo.net"
  title="PhishDestroy threat report for solidmaxgo.net"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>