Skip to security report
Domain security and threat intelligence
omgomg.store favicon

omgomg.store

In short

omgomg.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”

Resolved IP
188.114.97.3
Registered
Jul 11, 2026
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 4/91 Automated brand label: Google
OTX: 8 refs Sep 25, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 4. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Source evidenceVirusTotal 4 / 91 · OTX 8 references 5 sources

VirusTotal

4 / 91 engine detections

Open report

OTX

8 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Analysis

Critical
VirusTotal
4 / 91
OTX
8 community refs
Page captures
4

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Collected source details

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

URLScan · 2026-09-25T05:55:59Z

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"
}
Cloudflare Radar · 2026-09-25T06:30:17Z

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"
    ]
}
VirusTotal · 2026-10-07T21:15:03Z

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"
}

Questions about omgomg.store

Is omgomg.store legit?

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.

Is omgomg.store safe to connect a wallet?

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.

What should I do if I used omgomg.store?

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.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 4 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeadaptivebeeagentalexaalexa topall-domainsapeaksoft iosapple iosapple privateartemisascii textbankbanker+6 more
RegistrationCreated Jul 11, 2026 (103d)
Time to First Unavailability 19 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.
Technical detailsProvenance & timestamps
First DetectedSep 25, 2026
DOM Analysisanalyzed Oct 9, 2026score 81/100
Submitted URLhttps://omgomg.store/
Favicon Hash
Observed page title
omgomg
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 48 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • beau.ns.cloudflare.com
  • dee.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-10 17:12:11
Valid until
2026-12-09 18:12:07
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-13 22:03:37 UTC
Collection source
PhishDestroy collector
Certificate fingerprint8776b9414f5df3fe0d0da835058955c12982f087e5fd765f550cccf8908f581d
Certificate names · 2 SANs
  • omgomg.store
  • *.omgomg.store

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

Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.omgomg.storeDomain record

The original observation time is not recorded for these hostnames.

Technologies · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of omgomg.store · checked Sep 25, 2026

100
Good
Performance
FCP
1.52s
First Contentful Paint
LCP
1.52s
Largest Contentful Paint
CLS
0.026
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.82s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

Last reachable observation

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

Stored observation history8

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

    Reachable→Unavailable

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

Earlier observations 3
  1. VirusTotal · Detection count

    1→5

  2. VirusTotal · Detection count

    0→1

  3. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    4/91 engine detections

    View source
  3. AlienVault OTX

    8 community references

    View source
  4. Added to PhishDestroy

    omgomg.store

    View source
  5. URLScan

    Page captured

    View source

Check for cloaking

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

omgomg.store

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 omgomg.store)
  • 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

Live Threat Feed Appeal This Listing
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/omgomg.store"
  title="PhishDestroy threat report for omgomg.store"
  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>