Skip to security report
Redirect recorded webmxeaz.comgoogle.com Details
webmxeaz.com favicon
Domain security and threat intelligence

webmxeaz.com

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

The webmxeaz.com page features a Russian-language giveaway interface promising two thousand Robux and asking users to complete a verification step. Visitors who interacted with the claim button should avoid entering account credentials or personal data.

Page title: “Google”

More about the sources
Recorded security signals

Use caution — do not enter credentials or personal information.

Spamhaus DBL: phishing domain
Registrar
United StatesDominet (HK)
Resolved IP
Canada172.67.161.49Cloudflare, Inc. · CDN
First seen by PhishDestroy
2026-11-20
Page captures
open gallery
Reports sent
view timeline
2026-11-20 1 Report Sent CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

ABUSE NOTICE · 24H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is domainabuse@service.aliyun.com. The latest stored availability evidence still shows the domain reachable; 2 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
2 days
Reports sent
1
Latest case ID
PD-AC5181066446642FBEE5
Current status
HTTP 302 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded webmxeaz.com on 2026-11-20. Risk: high (evidence score 65/100). Registrar: Dominet (HK). Status: Last known active. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

High
Status
Last known active
Hosting
Canada172.67.161.49Cloudflare, Inc. · CDN
Registrar
United StatesDominet (HK)
Page captures
5

URLScan capture · 2026-11-20 09:11 UTC · SHA-256 06349911…d90953c

PhishDestroy analysis, reviewed version

Robux prize claim layout and visual structure

The webmxeaz.com page is rendered in Russian against a dark background with a central white dialog card displaying game-related rewards. At the top of the card, it displays a currency symbol alongside the bold number "2000". Directly beneath this header, a banner states "ПОЗДРАВЛЯЕМ!" accompanied by an emoji. Further down, a purple badge indicates "ВЕРИФИКАЦИЯ", followed by the prominent heading "ТЫ ПОЛУЧИЛ 2000 РОБ НА СВОЙ АККАУНТ!". Below this text, a small prompt says "Подтверди, что ты человек и забери приз!" alongside a pointing finger emoji and instructions to click the button labeled "ПОЛУЧИТЬ".

Domain registration timeline and context

It was registered on 19 Nov 2026 and reported the same day, showing that the address was created through Dominet (HK) Limited right before public reports began. When evaluating unverified prize claims promising free in-game currency, a fresh registration date offers important context regarding the origin of the offer. Furthermore, it still responded on 20 Nov 2026 at 10:13 UTC.

What to check and how to respond

Free reward generators and verification steps typically lead to external survey offers, credential-harvesting forms, or app installation prompts designed to capture user data or monetize traffic. Visitors who reached this page should close the browser tab without clicking the verification button or entering account details. Anyone who already provided login credentials or personal information should immediately change their passwords and review their accounts for unauthorized activity.

Source evidence 5 sources

Spamhaus DBL

phishing domain

URLScan

Page capture

SHA-256 af5445fb…5e4240a

Open report
URLScanOriginal source recordObserved: 19 fields
Separate monitor record · 2026-11-21 04:30 UTC

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

UUID
01a1f839-ce35-75c9-a271-d42a0a824ccc
Score
0
Malicious
✗
Result at
2026-11-21T04:30:21Z
Enriched at
2026-11-21T09:12:14Z
Source timestamps
Urlscan result at: 2026-11-21 05:30:21; Urlscan enriched at: 2026-11-21 10:12:14

PhishDestroy DOM

15 / 100 · heuristic score · 0 brand references · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 15 / 100 · 2026-11-20 11:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
15
Analyzed at
2026-11-20T11:20:12Z
Source timestamp
2026-11-20 12:20:12
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
webmxeaz.com — Russian Robux prize claim page
AI description
webmxeaz.com displays a Russian Roblox currency giveaway asking visitors to complete verification. Review registration details before interacting.
AI summary
Robux prize claim layout and visual structure The webmxeaz.com page is rendered in Russian against a dark background with a central white dialog card displaying game-related rewards. At the top of the card, it displays a currency symbol alongside the bold number "2000". Directly beneath this header, a banner states "ПОЗДРАВЛЯЕМ!" accompanied by an emoji. Further down, a purple badge indicates "ВЕРИФИКАЦИЯ", followed by the prominent heading "ТЫ ПОЛУЧИЛ 2000 РОБ НА СВОЙ АККАУНТ!". Below this text, a small prompt says "Подтверди, что ты человек и забери приз!" alongside a pointing finger emoji and instructions to click the button labeled "ПОЛУЧИТЬ". Domain registration timeline and context It was registered on 19 Nov 2026 and reported the same day, showing that the address was created through Dominet (HK) Limited right before public reports began. When evaluating unverified prize claims promising free in-game currency, a fresh registration date offers important context regarding the origin of the offer. Furthermore, it still responded on 20 Nov 2026 at 10:13 UTC. What to check and how to respond Free reward generators and verification steps typically lead to external survey offers, credential-harvesting forms, or app installation prompts designed to capture user data or monetize traffic. Visitors who reached this page should close the browser tab without clicking the verification button or entering account details. Anyone who already provided login credentials or personal information should immediately change their passwords and review their accounts for unauthorized activity.
AI generated by
threat-v10-gemini
AI generated at
2026-11-20T09:17:09Z
Revision
af7099fedaac14920bef51a9debd170c1d9ae73fd27db1de7e4a803412f1ca65
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

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
VirusTotalOriginal source recordObserved: 14 fields
Open complete records
Website checksOriginal source recordRetrieved: 24 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Page title
Google

Trackers

Requests
11
Observed services
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    4
  • Name
    Google Beacons
    Company
    Google
    Country
    US
    Category
    Site Analytics
    Requests
    2
  • Name
    Google CSP Reporting
    Company
    Google
    Country
    US
    Category
    Utilities
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://www.gstatic.com/og/_/js/k=og.asy.en_US.ZVAFwZQ0iIs.2019.O/rt=j/m=_ac,_awd,ada,lldp,qads,abld/exm=/d=1/ed=1/rs=AA2YrTt2KH-gaFRxm7nSeyfdPmRkuvCWQw
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
302
Request timings, ms
DNS
0
Waiting
236
Download
1
Response time, ms
284

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

Carbon estimate

Bytes
199180
CO₂, grams
0.0073
Cleaner than, %
7

DNS servers

Nameservers
  • IP address
    172.64.35.147
    Host
    nico.ns.cloudflare.com
  • IP address
    172.64.34.246
    Host
    elly.ns.cloudflare.com
DNS zone
webmxeaz.com

Page quality

Layout shift (CLS)
0
SEO score
91
Speed Index, s
1.83
First Contentful Paint (FCP), s
1.83
Largest Contentful Paint (LCP), s
1.83
Total Blocking Time (TBT), ms
232.5
Performance score
94
Accessibility score
98
Best practices score
100

Cookies

Cookies
  • Name
    __Secure-STRP
    Secure
    Yes
    SameSite
    Strict
  • Name
    SEARCH_SAMESITE
    SameSite
    Strict
  • Name
    AEC
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    Lax
  • Name
    NID
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None

Location

IP address
2606:4700:3036::6815:5185
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Subject alternative names
  • *.webmxeaz.com
  • webmxeaz.com
Key size, bits
256
Certificate chain
  • webmxeaz.com
  • YE2
  • Root YE
  • ISRG Root X2
  • ISRG Root X1
Issuer
Let's Encrypt / YE2
Serial
0584F805694D2E7E498D64A33EF288C56AE0
SHA-256
134d55f9ff4c4ff1acacfc64d34af7dd54d3350ac1adf62df01eb79117c14363
Subject
webmxeaz.com
Valid until
Valid from

DNS records

A
  • 104.21.81.133
  • 172.67.161.49
NS
  • nico.ns.cloudflare.com
  • elly.ns.cloudflare.com
SOA
Primary nameserver
elly.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2420613128
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3036::6815:5185
  • 2606:4700:3034::ac43:a131

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000
Observation
HSTS header does not include all subdomains.

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
No
X-XSS-Protection
0
Permissions-Policy
unload=()
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
same-origin-allow-popups; report-to="gws"
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2606:4700:3036::6815:5185
IP version
6

Redirects

Redirect chain
  • https://webmxeaz.com
  • https://www.google.com/
Count
1

Technology stack

Technologies
  • Google Web Server
  • Priority Hints
  • HTTP/3

Page links

External link addresses
  • https://mail.google.com/mail/&ogbl
  • https://www.google.com/imghp
  • https://www.google.com/intl/en/about/products
  • https://accounts.google.com/ServiceLogin
  • https://about.google/
  • https://www.google.com/intl/en_ir/ads/
  • https://www.google.com/services/
  • https://google.com/search/howsearchworks/
  • https://policies.google.com/privacy
  • https://policies.google.com/terms
  • https://www.google.com/preferences
  • https://support.google.com/websearch/
Internal link addresses
  • https://webmxeaz.com/advanced_search
  • https://webmxeaz.com/history/privacyadvisor/search/unauth
  • https://webmxeaz.com/history/optout
External links
12
Internal links
3

Registration record

Registrar
Dominet (HK) Limited
Registrar IANA ID
3775
Registrar URL
http://www.alibabacloud.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • elly.ns.cloudflare.com
  • nico.ns.cloudflare.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
gws
Content-Type
text/html; charset=UTF-8
X-Frame-Options
SAMEORIGIN
Permissions-Policy
unload=()
Cross-Origin-Opener-Policy
same-origin-allow-popups; report-to="gws"
Link
</shared_dict/homepage/6da693baa51a2e9a82e782cc621c5838bcaf35c9b6de3a17fec70c80564485d2.dict>; rel="compression-dictionary"
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Page title and metadata
Title: Google
Trackers
Requests: 11; Trackers: (Name: Google Static; Company: Google; Country: US; Category: Hosting; Requests: 4), (Name: Google Beacons; Company: Google; Country: US; Category: Site Analytics; Requests: 2), (Name: Google CSP Reporting; Company: Google; Country: US; Category: Utilities; Requests: 1)
Forms and mixed content
No sri: https://www.gstatic.com/og/_/js/k=og.asy.en_US.ZVAFwZQ0iIs.2019.O/rt=j/m=_ac,_awd,ada,lldp,qads,abld/exm=/d=1/ed=1/rs=AA2YrTt2KH-gaFRxm7nSeyfdPmRkuvCWQw; Third party scripts: 1
Status
Up: ✓; Code: 302; Timings: DNS: 0; Wait: 236; Download: 1; Response ms: 284
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
Carbon
Bytes: 199180; Co2 grams: 0.0073; Cleaner than: 7
DNS server
NS: (IP: 172.64.35.147; Host: nico.ns.cloudflare.com), (IP: 172.64.34.246; Host: elly.ns.cloudflare.com); Zone: webmxeaz.com
Quality
Cls: 0; Seo: 91; Si s: 1.83; Fcp s: 1.83; Lcp s: 1.83; Tbt ms: 232.5; Performance: 94; Accessibility: 98; Best practices: 100
Cookies
Cookies: (Name: __Secure-STRP; Secure: ✓; Same site: Strict), (Name: SEARCH_SAMESITE; Same site: Strict), (Name: AEC; Secure: ✓; HTTP only: ✓; Same site: Lax), (Name: NID; Secure: ✓; HTTP only: ✓)
Location
IP: 2606:4700:3036::6815:5185; ASN: 13335; Org: Cloudflare, Inc.; City: Toronto; Country: CA
SSL
San: *.webmxeaz.com, webmxeaz.com; Bits: 256; Chain: webmxeaz.com, YE2, Root YE, ISRG Root X2, ISRG Root X1; Issuer: Let's Encrypt / YE2; Serial: 0584F805694D2E7E498D64A33EF288C56AE0; SHA256: 134d55f9ff4c4ff1acacfc64d34af7dd54d3350ac1adf62df01eb79117c14363; Subject: webmxeaz.com; Valid to: 2027-02-17T21:25:20Z; Valid from: 2026-11-19T21:25:21Z
DNS records
A: 104.21.81.133, 172.67.161.49; NS: nico.ns.cloudflare.com, elly.ns.cloudflare.com; Soa: Nsname: elly.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2420613128; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:3036::6815:5185, 2606:4700:3034::ac43:a131
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Header: max-age=31536000; Message: HSTS header does not include all subdomains.
HTTP security policies
Xframeoptions: SAMEORIGIN; Referrerpolicy: ✗; Xxssprotection: 0; Permissionspolicy: unload=(); Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: same-origin-allow-popups; report-to="gws"; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 2606:4700:3036::6815:5185; Family: 6
Redirects
Chain: https://webmxeaz.com, https://www.google.com/; Count: 1
Tech stack
Technologies: Google Web Server, Priority Hints, HTTP/3
Page links
External: https://mail.google.com/mail/&ogbl, https://www.google.com/imghp, https://www.google.com/intl/en/about/products, https://accounts.google.com/ServiceLogin, https://about.google/, https://www.google.com/intl/en_ir/ads/, https://www.google.com/services/, https://google.com/search/howsearchworks/, https://policies.google.com/privacy, https://policies.google.com/terms, https://www.google.com/preferences, https://support.google.com/websearch/; Internal: https://webmxeaz.com/advanced_search, https://webmxeaz.com/history/privacyadvisor/search/unauth, https://webmxeaz.com/history/optout; External count: 12; Internal count: 3
Registration record
Registrar: Dominet (HK) Limited; Registrar iana ID: 3775; Registrar URL: http://www.alibabacloud.com; Created: 2026-11-19T22:20:32Z; Updated: 2026-11-19T22:20:34Z; Expires: 2027-11-19T22:20:32Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: elly.ns.cloudflare.com, nico.ns.cloudflare.com; Dnssec: unsigned
HTTP headers
Headers: Server: gws; Content type: text/html; charset=UTF-8; X frame options: SAMEORIGIN; Permissions policy: unload=(); Cross origin opener policy: same-origin-allow-popups; report-to="gws"; Link: </shared_dict/homepage/6da693baa51a2e9a82e782cc621c5838bcaf35c9b6de3a17fec70c80564485d2.dict>; rel="compression-dictionary"

Questions about webmxeaz.com

Is webmxeaz.com officially affiliated with Roblox?

No, the page is not connected to Roblox Corporation in any official capacity. Because it was registered on 19 Nov 2026 and reported the same day, the domain lacks any established history as a legitimate platform.

What happens if I click the verification button on webmxeaz.com?

Clicking the claim button typically redirects visitors to external ad networks, third-party surveys, or credential-stealing login prompts. It does not deposit Robux into any personal account.

What should I do if I entered my password on webmxeaz.com?

Anyone who submitted account details should log into their official Roblox account immediately to change the password and enable two-factor authentication.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (5)

All capture links and hashes (5)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 88 report ↗
IP Context Canada172.67.161.49 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Dominet (HK) US(US)
RegistrationExpires 2027-11-19
Registrant countryUnited States VirusTotal WHOIS
Registrant6aacf85c31f44448s@ VirusTotal WHOIS
HTTP Status302 Found (Temporary)
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-20
DOM Analysisanalyzed 2026-11-20score 15/100
Submitted URLhttps://webmxeaz.com/b/2044?… query redacted
Case ID
Observed page title
Google
TLS Certificate
Issued by YE2 · stored validity ends in 87 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.67.161.49
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • elly.ns.cloudflare.com
  • nico.ns.cloudflare.com

SOA

  • nsname: elly.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2420613128
  • 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-11-19 21:25:21
Valid until
2027-02-17 21:25:20
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint134d55f9ff4c4ff1acacfc64d34af7dd54d3350ac1adf62df01eb79117c14363
Certificate names · 2 SANs
  • *.webmxeaz.com
  • webmxeaz.com

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

Latest Classified Outcome 2026-11-21 11:13 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting DNS: Resolved
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-21 11:13 UTC
RDAP registration
Observed timeline last reachable: 2026-11-21 11:13 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 3 identified
Open complete records
PageSpeed (mobile): 89

Google PageSpeed Insights — mobile performance audit of webmxeaz.com ·

89
Needs Work
Performance
FCP
2 s
First Contentful Paint
LCP
3.52 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
2 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://webmxeaz.com/b/2044
MAX
MAX — мессенджер
Response
HTTP 200
HTML body
9.4 KB
Compressed
3.0 KB
Links
0 internal · 0 external
Detected technologies
reactcloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Server: cloudflare
Security headers present
Strict-Transport-SecurityX-Content-Type-OptionsReferrer-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Twitter card: summary_large_image
Saved response-header values · 20
Alt-Svc
h3=":443"; ma=86400
Cache-Control
no-store, no-cache, must-revalidate, max-age=0
cf-cache-status
DYNAMIC
CF-RAY
a5d657a84c3ff5bc-AMS
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy-Report-Only
default-src 'self'; script-src 'self' 'nonce-pA_sxMAx40_aDo7fhEB9ag3W' https://telegram.org https://st.max.ru; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self'; object-src 'none'
Content-Type
text/html; charset=utf-8
Date
Fri, 20 Nov 2026 09:14:05 GMT
Expires
0
NEL
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Pragma
no-cache
Referrer-Policy
same-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=G5ar%2B7EHnmbicxaGsO3zdAXJcJJI9A6a1q0CC5kEdzVwnAaPlf6b39Glk1A0jOfDgqUxr1MfzRhQj1RTxuwObDFwIlJ7HlV9pW7QoQcSW6amnHBqjV6%2BUZ8tTDumDFA%3D"}]}
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-Request-ID
6f04f4e5ba8d4003834a775d68b910f1

Values retained by the collector; long values may be shortened during collection.

Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

All stored data110
Open complete records

Captured network requests

Network requests: 14 SHA-256 hashes: 14 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-20 09:14 UTC.

Open this scan on URLScan 01a1f839-ce35-75c9-a271-d42a0a824ccc ↗

Stored observation history3

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

    Redirecting elsewhere

    HTTP redirect

  2. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  3. Domain monitor · First collection record

    Reachable

All retained availability observations7
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · in progress

Recorded events: 10. 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
  • Threat Ingested
    webmxeaz.com detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Automated brand label: Google · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Dominet (HK) Limited. Abuse contacts: 1.
    • domainabuse@service.aliyun.com
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

3 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+10 h 52 min
  3. First abuse report sent+4 min

Reported 10 h 56 min after registration

  1. Abuse report sent

    PD-AC5181066446642FBEE5 · Receipt 85404

    domainabuse@service.aliyun.com
    +4 min
  2. Added to PhishDestroy

    webmxeaz.com

    same minute
  3. URLScan

    Page captured

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.

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.

webmxeaz.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-AC5181066446642FBEE5 Recipient: domainabuse@service.aliyun.com
Page title stored with report: MAX
PDF notice generated
Deep Analysis

Were You Affected by This Site?

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. Secure your accounts and funds first, then report. 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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

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.

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
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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 webmxeaz.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

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.

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/webmxeaz.com"
  title="PhishDestroy threat report for webmxeaz.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>