Cloudflare Radar
Suspicious
Open reportThis 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: “ВАМ ПОДАРИЛИ КОЛЕЧКО 💍”
Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
URLScan capture · 2026-11-12 22:15 UTC · SHA-256 11efaa03…80b6755
PhishDestroy analysis, reviewed version
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.
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.
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.
Suspicious
Open report1/100
spam domain
Page capture
SHA-256 304e7b84…4475146
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| 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 |
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.
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.
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.
Edge-IP reputation is not attributed to this domain.
hasslo.ns.cloudflare.comrobin.ns.cloudflare.comnsname: hasslo.ns.cloudflare.comhostmaster: dns.cloudflare.comserial: 2419958239refresh: 10000retry: 2400expire: 604800minttl: 1800Location describes the IP network.
ad63e58ad70fdbd12711512d21d4b0ddc2deaa1ed180053fd3d358a7e72fd342*.solidmaxgo.netsolidmaxgo.netSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The domain no longer resolves in DNS.
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://solidmaxgo.net/w/iwiXJizysContent-Type: text/html; charset=utf-8Server: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gzipe7916b397714f7b72120cc48a568a15e16862707257f2954babd87c8a91ec36eh3=":443"; ma=86400DYNAMICa598e109ce1cfba5-AMSkeep-alivegziptext/html; charset=utf-8Thu, 12 Nov 2026 22:12:35 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=2OYjUVrKcuQ1IDJuWUN7vltvFsFtaYBSSK6w23An9zowhrL2ggRiFdv%2BknutPMnwXaxEmkqEoTigb%2BZaelmfU8G6rs5bwzgf0fqgV%2FmW9UwSK7f8zJ7rggLmO2RF1LCrMw%3D%3D"cloudflarecfCacheStatus;desc="DYNAMIC"chunkedValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Not resolving in DNS
domain does not exist in DNS
Redirecting elsewhere
HTTP redirect
Reachable
Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 13 h 56 min after registration
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
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| ID | Stored data |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
solidmaxgo.net PD-B7BB238024B6C6599AE5 Recipient: abuse@ordertld.com 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.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
solidmaxgo.net)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.