Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 1/92 engines flagged. malicious: 0. suspicious: 1. Analysis time (as stored): 2026-11-03T02:04:08Z. Retrieved (as stored): 2026-11-04T21:10:10Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Redirect recorded gamowex.comgoogle.com Details
Domain security and threat intelligence
gamowex.com favicon

gamowex.com

In short

PhishDestroy first recorded gamowex.com on 2026-11-04. Stored VirusTotal result: 1/92 engines flagged. malicious: 0. suspicious: 1. Analysis time (as stored): 2026-11-03T02:04:08Z. Retrieved (as stored): 2026-11-04T21:10:10Z. Google Safe Browsing flags it.

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Canada104.21.25.14Cloudflare, Inc. · CDN
Registered
Oct 31, 2026
First observed
Nov 4, 2026
PhishDestroy assessment Critical
80/100
Evidence score
First observed Nov 4, 2026 19:45 UTC · PhishDestroy
Risk signals
VirusTotal detections: 1/92 Young domain: 4 days old Google Safe Browsing: threat flag recorded
VirusTotal
1 / 92
engine detections ·
Google Safe Browsing
Flagged
OTX
2
community references
Page captures
1
open gallery
Domain age
4 days
registered 2026-10-31 according to WHOIS
OTX: 2 refs Nov 4, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded gamowex.com on 2026-11-04. Stored VirusTotal result: 1/92 engines flagged. malicious: 0. suspicious: 1. Analysis time (as stored): 2026-11-03T02:04:08Z. Retrieved (as stored): 2026-11-04T21:10:10Z. Google Safe Browsing flags it. Risk: critical (80/100). Registrar: Dynadot. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

Critical
VirusTotal
1 / 92
Hosting
Canada104.21.25.14Cloudflare, Inc. · CDN
Registrar
United StatesDynadot
Registered
Oct 31, 2026
OTX
2 community refs
Page captures
1
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for gamowex.com. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 1 / 92 · Google Safe Browsing: flagged · OTX 2 references 5 sources

VirusTotal

1 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
0
Suspicious
1
Undetected
38

Vendor labels

Gridinsoft
suspicious

Reputation score

0

Registrar

Dynadot Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    172.67.221.143
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    john.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.25.14
  • TTL, seconds
    21600
    Type
    NS
    Value
    treasure.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    john.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.gamowex.com
  • gamowex.com
Issuer
Let's Encrypt / YE2
Serial
566ab1ba5d0ccfbf1cf6b24a64ab0f25522
SHA-256
939fbc385431b2f4982d46c4803b831454194e4b334fbfd65d6e3c18d52cf7eb
Subject
gamowex.com
Valid until
Valid from

Registration record

Registrar
Dynadot Inc
Registrar IANA ID
472
Registrar URL
http://www.dynadot.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • john.ns.cloudflare.com
  • treasure.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 0,
    "suspicious": 1,
    "undetected": 38
}
Vendor labels
{
    "Gridinsoft": "suspicious"
}
Reputation
0
Registrar
Dynadot Inc
Created
2026-10-31T07:03:18Z
Expires
2027-10-31T07:03:18Z
Updated
2026-10-31T07:06:00Z
First seen
2026-10-31T08:11:27Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.221.143"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "john.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.25.14"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "treasure.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "john.ns.cloudflare.com"
    }
]
Dns at
2026-11-03T02:04:43Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.gamowex.com",
        "gamowex.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "566ab1ba5d0ccfbf1cf6b24a64ab0f25522",
    "sha256": "939fbc385431b2f4982d46c4803b831454194e4b334fbfd65d6e3c18d52cf7eb",
    "subject": "gamowex.com",
    "valid_to": "2027-01-29T06:13:33Z",
    "valid_from": "2026-10-31T06:13:34Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-10-31T07:03:18Z",
    "updated": "2026-10-31T07:06:00Z",
    "expires": "2027-10-31T07:03:18Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "john.ns.cloudflare.com",
        "treasure.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-31T07:03:18Z",
        "last changed": "2026-10-31T07:06:00Z",
        "registration": "2026-10-31T07:03:18Z",
        "registrar expiration": "2027-10-31T07:03:18Z",
        "last update of RDAP database": "2026-10-31T07:11:10Z"
    }
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
1
denominator
92
malicious
null
suspicious
null
vendors
["Gridinsoft"]
observed_at
2026-11-03 02:04:08
checked_at
2026-11-04 22:10:21
fetched_at
2026-11-04 21:10:22
time_basis
as stored; legacy timezone not established

Google Safe Browsing

Threat flag recorded

Open report

OTX

2 community references

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 1 field

Observed: · Retrieved:

Report ID

a22c7627-c0d1-4279-9e81-3d120363ddcd
Original source fields · JSON
Uuid
a22c7627-c0d1-4279-9e81-3d120363ddcd

URLScan

Page capture

SHA-256 abd1642476374df55d06bc1bc5b6e2c14a1996e44e13b9517db8b19533ad105b

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a19e72-8653-714f-9f84-eeb5aec3ce34

Final URL

https://gamowex.com/

HTTP response

666

Redirect type

https-only

Redirects

  • To
    https://gamowex.com/
    From
    http://gamowex.com/
    Status
    307

IP address

172.67.221.143

Contacted domains

  • www.google.com
  • static.cloudflareinsights.com

Contacted IP addresses

  • 142.251.151.119
  • 104.16.80.73
  • 172.67.221.143

Autonomous systems (ASN)

  • 15169
  • 13335

Server countries

  • US

Document hash

abd1642476374df55d06bc1bc5b6e2c14a1996e44e13b9517db8b19533ad105b

Script hashes

  • 0bf32f6f5e0db7af1e5c2bf8701b0dda03b6b9fc7f09c66755a85200506b3a0b

TLS session and certificate

Subject alternative names
  • *.gamowex.com
  • gamowex.com
Cipher
AES_128_GCM
Issuer
YE2
Subject
gamowex.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1

Registered domain age, days

1

Certificate age, days

2

Certificate validity, days

89

Page requests

6

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
-5
Malicious
No
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a19e72-8653-714f-9f84-eeb5aec3ce34
Final url
https://gamowex.com/
Status
666
Redirected
https-only
Redirects
[
    {
        "to": "https://gamowex.com/",
        "from": "http://gamowex.com/",
        "status": 307
    }
]
Ip
172.67.221.143
Contacted domains
[
    "www.google.com",
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "142.251.151.119",
    "104.16.80.73",
    "172.67.221.143"
]
Asns
[
    "15169",
    "13335"
]
Countries
[
    "US"
]
Document hash
abd1642476374df55d06bc1bc5b6e2c14a1996e44e13b9517db8b19533ad105b
Script hashes
[
    "0bf32f6f5e0db7af1e5c2bf8701b0dda03b6b9fc7f09c66755a85200506b3a0b"
]
Tls
{
    "san": [
        "*.gamowex.com",
        "gamowex.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "gamowex.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-29T06:13:33Z",
    "valid_from": "2026-10-31T06:13:34Z"
}
Domain age days
1
Apex age days
1
Tls age days
2
Tls valid days
89
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -5,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a19e72-8653-714f-9f84-eeb5aec3ce34
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
Website checksOriginal source recordRetrieved: 15 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.34.116
    Host
    treasure.ns.cloudflare.com
  • IP address
    172.64.33.185
    Host
    john.ns.cloudflare.com
DNS zone
gamowex.com

Location

IP address
172.67.221.143
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
gamowex.com

DNS records

A
  • 172.67.221.143
  • 104.21.25.14
NS
  • treasure.ns.cloudflare.com
  • john.ns.cloudflare.com
SOA
Primary nameserver
john.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418917786
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

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
172.67.221.143
IP version
4

Technology stack

Technologies
  • Cloudflare

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • john.ns.cloudflare.com
  • treasure.ns.cloudflare.com
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": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.34.116",
            "host": "treasure.ns.cloudflare.com"
        },
        {
            "ip": "172.64.33.185",
            "host": "john.ns.cloudflare.com"
        }
    ],
    "zone": "gamowex.com"
}
Location
{
    "ip": "172.67.221.143",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "gamowex.com"
}
DNS records
{
    "A": [
        "172.67.221.143",
        "104.21.25.14"
    ],
    "NS": [
        "treasure.ns.cloudflare.com",
        "john.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"john.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418917786, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "172.67.221.143",
    "family": 4
}
Tech stack
{
    "technologies": [
        "Cloudflare"
    ]
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-31T07:03:18Z",
    "updated": "2026-10-31T07:06:00Z",
    "expires": "2027-10-31T07:03:18Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "john.ns.cloudflare.com",
        "treasure.ns.cloudflare.com"
    ]
}

Questions about gamowex.com

Is gamowex.com legit?

PhishDestroy rates gamowex.com as critical risk (80/100) from the recorded evidence; it was first recorded on 2026-11-04. Stored VirusTotal result: 1/92 engines flagged. malicious: 0. suspicious: 1. Analysis time (as stored): 2026-11-03T02:04:08Z. Retrieved (as stored): 2026-11-04T21:10:10Z. Google Safe Browsing flags it. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is gamowex.com safe to connect a wallet?

This report does not record which wallet requests gamowex.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used gamowex.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 1 capture

URLScan · 2026-11-04 → www.google.com 1 / 1
SourceURLScan · 2026-11-04 → www.google.com
Recorded
StateStored capture
HTTP status200
Final URLhttps://www.google.com/chrome/
Position1 / 1
Open capture Source Report Wayback Download
All capture links and hashes (1)

Domain details

Domain
Google Safe Browsing Flagged Social engineering checked Nov 4, 2026
IP Context Canada104.21.25.14 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-11all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contact["abuse@dynadot.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for gamowex.com →
RegistrationCreated Oct 31, 2026 (4d · Brand New!) — Expires Oct 31, 2027
WHOIS statusclientTransferProhibited
Technical detailsProvenance & timestamps
First DetectedNov 4, 2026
Submitted URLhttp://gamowex.com/
Favicon Hash
TLS Certificate
Issued by YE2 · stored validity ends in 85 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada104.21.25.14
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • treasure.ns.cloudflare.com
  • john.ns.cloudflare.com

SOA

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

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
YE2
Valid from
2026-10-31 06:13:34
Valid until
2027-01-29 06:13:33
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint939fbc385431b2f4982d46c4803b831454194e4b334fbfd65d6e3c18d52cf7eb
Certificate names · 2 SANs
  • *.gamowex.com
  • gamowex.com

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

viewdns.info · 104.21.25.14rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

1 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 1 detection
Gridinsoft

Captured network requests

Network requests: 6 SHA-256 hashes: 5 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-04 19:50 UTC.

Open this scan on URLScan 01a19e72-8653-714f-9f84-eeb5aec3ce34 ↗

Stored observation history1

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

  1. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    666
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 20:45:56.000000
    Evidence SHA-256
    cad3e5168a223d22ed62687898abf6626b5c4e25ef3a77d97736bb81f7f73343
    HTTP probe value as recorded
    666
    Evidence timestamp as recorded
    2026-11-04 20:45:56
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    666
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 20:45:56.000000
    Evidence SHA-256
    cad3e5168a223d22ed62687898abf6626b5c4e25ef3a77d97736bb81f7f73343
    HTTP probe value as recorded
    666
    Evidence timestamp as recorded
    2026-11-04 20:45:56
    Evidence reason

Threat Response Pipeline

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

Recorded events: 8. 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: 1 of 1
  • Threat Ingested
    gamowex.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · OTX Community References · Forensic Evidence Collected Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 1/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • OTX Community References
    Community publication references on AlienVault OTX: 2. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

4 entries
  1. AlienVault OTX

    2 community references

    View source
  2. Google Safe Browsing

    Threat flag recorded

    View source
  3. Added to PhishDestroy

    gamowex.com

    View source
  4. VirusTotal

    1/92 engine detections

    View source
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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
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.

gamowex.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 1 det. ChainPatrol URLQuery Google SB Flagged SSL Labs Stored certificate dates valid CF Radar Open report OTX 2 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Unverified
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. Silence is the scammer’s greatest advantage. Break it.
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • 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

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 gamowex.com)
  • 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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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.

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.

Request a correction or appeal How PhishDestroy works
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/gamowex.com"
  title="PhishDestroy threat report for gamowex.com"
  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>