VirusTotal
4 / 91 engine detections
Open reportomgomg.store is a Google impersonation page detected by PhishDestroy on 2026-09-25. Risk: critical (81/100). Status: Content unavailable. Hosting: Cloudflare, Inc. VirusTotal: 4/91 engines flag it. Do not enter credentials or connect a wallet.
“omgomg”
4 / 91 engine detections
Open report8 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
omgomg.store is an impersonation phishing page: a site built to pass itself off as a legitimate service so visitors trust it with their credentials or money. PhishDestroy first saw it on 2026-09-25. Its page title showed only "omgomg" and did not name the brand it imitated, but we classified it as impersonation phishing. The site went offline on 2026-10-14 and was still dead when last checked on 2026-10-19.
Impersonation pages copy the look and wording of a service the victim already uses, then present a login form, account "verification" step or payment prompt. Anything typed in goes to the operators. Stolen passwords and one-time codes are used to take over the real account. Payments made on the fake site are simply kept. The bare "omgomg" title points to a short-lived throwaway domain rather than an established business.
VirusTotal results from 2026-10-06 show 4 of 91 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and Gridinsoft. That is a low count, so many browsers and security tools would have shown no warning to visitors. The domain also appears in 8 AlienVault OTX threat pulses, which means other researchers tracked it independently. PhishDestroy is the only blocklist listing it.
The domain resolved to an address on Cloudflare's network, geolocated to Canada. That means the real origin server sat behind Cloudflare's proxy and was not exposed. Its TLS certificate came from Google Trust Services (WE1), the standard certificate for Cloudflare-fronted sites. The padlock in the browser therefore said nothing about whether the site was legitimate. The site ran for roughly three weeks after we first saw it before going dark.
If you entered a password on omgomg.store, change it on the genuine service and on any account that uses the same password. Then turn on app-based two-factor authentication and sign out of all active sessions. If you gave a one-time code or recovery phrase, treat that account as compromised and move any funds it controls. If you paid through the site, contact your bank or card issuer immediately to dispute the charge. Security teams should block the domain, search proxy and DNS logs for visits since 2026-09-25, and reset credentials for any users who reached it.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0d722-6dee-73be-9bbe-b4dfea1ac602 |
|---|---|
| Final url | https://omgomg.store/ |
| Status | 200 |
| Ip | 104.21.16.165 |
| Contacted domains | [
"static.cloudflareinsights.com"
] |
| Contacted IP addresses | [
"104.16.80.73",
"104.21.16.165"
] |
| Asns | [
"13335"
] |
| Document hash | 9312c4f6001eead66eafdf6f1cc5447ed17525b2dd72a94b8d7b673faa7062ef |
| Globals | [
"requestResize",
"__cfBeacon"
] |
| Cookies | [
"antibot"
] |
| Tls | {
"san": [
"omgomg.store",
"*.omgomg.store"
],
"cipher": "AES_128_GCM",
"issuer": "WE1",
"subject": "omgomg.store",
"protocol": "TLS 1.2",
"valid_to": "2026-12-09T18:12:07Z",
"valid_from": "2026-09-10T17:12:11Z"
} |
| Domain age days | 1526 |
| Apex age days | 1526 |
| Tls age days | 14 |
| Tls valid days | 90 |
| Requests | 5 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 93,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=utf-8"
} |
Observed: · Retrieved:
| Uuid | 5fe06fc5-babe-4c13-8e05-d1678bab3c0a |
|---|---|
| Final url | https://omgomg.store/ |
| Status | 200 |
| History | [
{
"url": "https://omgomg.store/",
"status": 200
}
] |
| DOM structure hash | 39a29eb19730275131d844181f4dfbca198b429e35cd6fe7383e0d8cb6eae35f |
| Document hash | 4b070735e244b1b51c8c706b7deff3223eb1ad691975f35099701e62660455c9 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "omgomg.store",
"type": "A",
"value": "172.67.214.219"
},
{
"name": "omgomg.store",
"type": "A",
"value": "104.21.16.165"
}
] |
| Dnssec valid | false |
| Ip | 172.67.214.219 |
| Registration record | {
"registrar": "Fewmoretaps OU d/b/a Trustname.com",
"created": "2026-07-11T11:11:34Z",
"updated": "2026-07-16T11:12:31Z",
"expires": "2027-07-11T11:11:34Z",
"nameservers": [
"beau.ns.cloudflare.com",
"dee.ns.cloudflare.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 54,
"malicious": 3,
"suspicious": 1,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"G-Data": "phishing",
"alphaMountain.ai": "suspicious",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Business/Economy, Suspicious (alphaMountain.ai)"
} |
| Popularity | {
"Majestic": 998129,
"Cisco Umbrella": 395846
} |
| Created | 2026-07-06T00:00:00Z |
| Updated | 2026-07-06T00:00:00Z |
| First seen | 2023-10-22T10:05:49Z |
| DNS records | [
{
"ttl": 300,
"type": "A",
"value": "172.67.214.219"
},
{
"ttl": 300,
"type": "A",
"value": "104.21.16.165"
},
{
"ttl": 21600,
"type": "NS",
"value": "dee.ns.cloudflare.com"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "beau.ns.cloudflare.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "beau.ns.cloudflare.com"
}
] |
| Dns at | 2026-09-26T03:55:04Z |
| Jarm | 27d40d40d00040d1dc27d40d27d40d5fb4c89fe3813d172ffb53f84a68f750 |
| Certificate | {
"san": [
"omgomg.store",
"*.omgomg.store"
],
"issuer": "Google Trust Services / WE1",
"serial": "64c127390f984a8e0e1974c806a70977",
"sha256": "8776b9414f5df3fe0d0da835058955c12982f087e5fd765f550cccf8908f581d",
"subject": "omgomg.store",
"valid_to": "2026-12-09T18:12:07Z",
"valid_from": "2026-09-10T17:12:11Z"
} |
| Registry data | {
"status": [
"active"
],
"events": {
"expiration": "2027-07-11T11:11:34Z",
"last changed": "2026-07-13T13:54:59Z",
"registration": "2026-07-11T11:11:34Z",
"registrar expiration": "2027-07-11T11:11:34Z",
"last update of RDAP database": "2026-10-01T01:59:37Z"
},
"registrar": "Fewmoretaps OU d/b/a Trustname.com",
"registrar_iana_id": "4318"
} |
No. PhishDestroy classifies omgomg.store as a Google impersonation page (risk: critical, 81/100); it was first detected on 2026-09-25. VirusTotal: 4/91 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on omgomg.store. 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.
Edge-IP reputation is not attributed to this domain.
beau.ns.cloudflare.comdee.ns.cloudflare.comLocation describes the IP network.
8776b9414f5df3fe0d0da835058955c12982f087e5fd765f550cccf8908f581domgomg.store*.omgomg.storeSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.omgomg.storeDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of omgomg.store · checked Sep 25, 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.
Reachable→Unavailable
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
1→5
0→1
Reachable
No threat flag
View source4/91 engine detections
View source8 community references
View sourceomgomg.store
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
omgomg.store
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 ↗
omgomg.store)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.