VirusTotal
14 / 90 engine detections
Open reportgo-for-free-verify-badge-here.surge.sh is a Facebook impersonation page detected by PhishDestroy on 2026-09-02. Risk: critical (95/100). Registrar: Surge.sh. Status: Content unavailable. Hosting: DigitalOcean, LLC. VirusTotal: 14/90 engines flag it. Do not enter credentials or connect a wallet.
“Unavailable”
14 / 90 engine detections
Open reportMalicious
Open reportMalicious
Open reportno community references
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
go-for-free-verify-badge-here.surge.sh is an impersonation phishing page that poses as Facebook. Its subdomain promises a free verification badge, a lure aimed at page owners, creators and admins who want the blue check. PhishDestroy first saw it on 2026-09-02. The site has been offline since 2026-09-08, with its content blocked by the hosting provider, and it was still dead at the last check on 2026-10-19.
Fake badge offers usually arrive through messages or comments claiming the target qualifies for free verification. The link leads to a form styled like Facebook that asks for the account login and often the two-factor code, which hands the attacker full control of the profile and any pages or ad accounts tied to it. Hijacked accounts are then used to run scams, spread the same lure to new victims or extract payment from the owner. The page title currently reads "Unavailable", while we classified the site as a Facebook impersonation page.
On 2026-09-04, 14 of 90 VirusTotal engines flagged the address, including BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Emsisoft, Gridinsoft, alphaMountain.ai and Chong Lua Dao. That is a moderate count, but the vendors are independent of one another and agree on the verdict. urlscan.io rated the page malicious and recognized Facebook branding on it. PhishDestroy lists it on its own blocklist.
The page sat on Surge.sh, a free static-site publishing service, so the operator only had to pick a subdomain name rather than register a domain. It resolved to DigitalOcean, LLC infrastructure in Canada and carried a domain-validated Sectigo certificate inherited from the platform. Throwaway subdomains like this are cheap to create and abandon, which matches the short window between first sighting and the takedown on 2026-09-08.
If you entered your Facebook login here, change the password immediately, enable an authenticator app for two-factor authentication, and log out all other sessions from the account's security settings. Review page roles, ad accounts and linked email addresses for changes you did not make, and report the compromise through Facebook's hacked-account flow. Facebook does not hand out badges through external links, so treat any such offer as a scam. Defenders should block the subdomain and watch for similar badge-themed hosts on free publishing platforms.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0624b-721c-76ef-b09b-4d2455565a40 |
|---|---|
| Final url | https://go-for-free-verify-badge-here.surge.sh/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://go-for-free-verify-badge-here.surge.sh/",
"from": "http://go-for-free-verify-badge-here.surge.sh/",
"status": 307
}
] |
| Ip | 46.101.67.123 |
| Contacted domains | [
"link-of-video-step3.wasmer.app",
"cdnjs.cloudflare.com",
"logo-ver.vercel.app",
"resource2.heygen.ai"
] |
| Contacted IP addresses | [
"5.78.26.104",
"216.198.79.195",
"104.17.25.14",
"46.101.67.123"
] |
| Asns | [
"212317",
"16509",
"13335",
"14061"
] |
| Countries | [
"US",
"GB"
] |
| Document hash | 3cb28ba98eb7cb2b1b699cb3207956d3377b8907adbaa07e08c48c3cef4c2f70 |
| Tls | {
"san": [
"*.surge.sh",
"surge.sh"
],
"cipher": "AES_256_GCM",
"issuer": "Sectigo Public Server Authentication CA DV R36",
"subject": "*.surge.sh",
"protocol": "TLS 1.3",
"valid_to": "2026-12-16T23:59:59Z",
"valid_from": "2026-06-01T00:00:00Z"
} |
| Domain age days | 0 |
| Apex age days | 4212 |
| Tls age days | 93 |
| Tls valid days | 198 |
| Requests | 9 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 97,
"malicious": true
},
"overall": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"facebook"
],
"malicious": true,
"categories": [
"phishing"
]
},
"urlscan": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"Facebook"
],
"malicious": true,
"categories": [
"phishing"
]
}
} |
| HTTP headers | {
"server": "Surge",
"content-type": "text/html; charset=UTF-8"
} |
Observed: · Retrieved:
| Uuid | ff13f4aa-7671-4c30-b475-c45bd4a64788 |
|---|---|
| Final url | https://go-for-free-verify-badge-here.surge.sh/ |
| Status | 200 |
| Redirected | https-only |
| History | [
{
"url": "http://go-for-free-verify-badge-here.surge.sh/",
"status": 307
},
{
"url": "https://go-for-free-verify-badge-here.surge.sh/",
"status": 200
}
] |
| DOM structure hash | 1a97b39d4c29667ce5786f07726b792aabb8f3e23a328c7a98a706d6dc29cbd0 |
| Document hash | 3cb28ba98eb7cb2b1b699cb3207956d3377b8907adbaa07e08c48c3cef4c2f70 |
| Phishing v2 | [
"phishing"
] |
| Domain risks | [
"Phishing",
"Security threats",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "go-for-free-verify-badge-here.surge.sh",
"type": "A",
"value": "159.203.50.177"
}
] |
| Dnssec valid | false |
| Ip | 159.203.50.177 |
| Verdict | {
"tags": [
"phishing"
],
"malicious": true,
"categories": [
"phishing"
]
} |
| Registration record | {
"registrar": "Porkbun LLC",
"created": "2014-07-25T23:10:53Z",
"updated": "2026-08-11T20:27:40Z",
"expires": "2027-07-25T23:10:53Z",
"nameservers": [
"ns1.surge.world",
"ns2.surge.world",
"ns3.surge.world",
"ns4.surge.world"
]
} |
No. PhishDestroy classifies go-for-free-verify-badge-here.surge.sh as a Facebook impersonation page (risk: critical, 95/100); it was first detected on 2026-09-02. VirusTotal: 14/90 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on go-for-free-verify-badge-here.surge.sh. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Location describes the IP network.
97b6f955e414ca95a3c57ecae57c2cba8532736157112d6cc11f56a5a790058asurge.shSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of go-for-free-verify-badge-here.surge.sh · checked Sep 2, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→blocked
http_451_blocked · http_451_unavailable
Unknown→blocked
http_451_blocked · http_451_unavailable
Unknown→blocked
http_451_blocked · http_451_unavailable
Unknown→blocked
http_451_blocked · http_451_unavailable
Unknown→blocked
http_451_blocked · http_451_unavailable
Unknown→blocked
http_451_blocked · http_451_unavailable
Unknown→blocked
http_451_blocked · http_451_unavailable
Unknown→blocked
http_451_blocked · http_451_unavailable
Unknown→blocked
http_451_blocked · http_451_unavailable
Unknown→blocked
http_451_blocked · http_451_unavailable
Reachable→Unavailable
15→14
12→15
Reachable
No threat flag
View source14/90 engine detections
View sourcego-for-free-verify-badge-here.surge.sh
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
go-for-free-verify-badge-here.surge.sh
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose 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 ↗
go-for-free-verify-badge-here.surge.sh)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.