Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
x-pay.help favicon

x-pay.help

In short

x-pay.help is a blocklisted domain detected by PhishDestroy on 2026-10-26.

“Xpay”

Review the evidence
Registrar
SingaporeGname
Resolved IP
Canada172.67.187.76Cloudflare, Inc. · CDN
Registered
Oct 20, 2026
First observed
Oct 26, 2026
PhishDestroy assessment Critical
75/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
Stored blocklist matches: 2 Young domain: 8 days old
VirusTotal
0 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
URLScan
Malicious
engine verdict · score 97
Cloudflare Radar
Phishing
Page captures
7
open gallery
Domain age
8 days
Reports sent
1
view timeline
Oct 26, 2026 1 Report Sent CDN
X Telegram API
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 complaint@gname.com. The latest stored availability evidence still shows the domain reachable; 44 hours 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
44 hours
Reports sent
1
Latest case ID
PD-20261026-7AF4AA
Current status
HTTP 200 at latest stored check

Analysis

Domain summary

x-pay.help is a blocklisted domain detected by PhishDestroy on 2026-10-26. Risk: critical (75/100). Registrar: Gname. Status: Last known active. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
0 / 92
Blocklist matches
2
Hosting
Canada172.67.187.76Cloudflare, Inc. · CDN
Registrar
SingaporeGname
Registered
Oct 20, 2026
Page captures
7
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy listed x-pay.help on its internal blocklist as a suspicious domain based on an admin report. The domain was first observed on 2026-10-26, six days after its registration on 2026-10-20, and returned HTTP 200 with the page title “Xpay”.

How the scam works

No malicious forms, wallet prompts, or credential fields were captured; the page only displays the title “Xpay”, which could be meant to resemble a payment service. Without such elements the listing cannot confirm a specific phishing or wallet‑draining technique, leaving only the generic risk that a newly registered domain might be used for deceptive offers.

Evidence

VirusTotal scanned the domain on 2026-10-21 with 92 engines and reported zero malicious or suspicious detections. Google Safe Browsing checked it on 2026-10-26 and did not flag it, while URLScan captured the site on 2026-10-23 and returned a clean verdict. Cloudflare Radar on 2026-10-26 labeled the domain as “phishing” and noted risks such as “Newly Seen Domains”, OTX had zero pulses, external blocklists showed none, and PhishDestroy’s internal list marks it as blocked.

Infrastructure

The domain was registered with Gname.com Pte. Ltd. on 2026-10-20 (expires 2027-10-20) and uses Cloudflare nameservers amy.ns.cloudflare.com and cleo.ns.cloudflare.com with A records 104.21.80.228, 172.67.187.76 and AAAA records 2606:4700:3031::ac43:bb4c, 2606:4700:3037::6815:50e4. It presented a Let’s Encrypt certificate for *.x-pay.help valid from 2026-10-20 to 2027-01-18 and was hosted on Cloudflare’s network in Canada; DNSSEC was not enabled and ports 80, 443, 8080 were open.

What to do

If you entered any credentials on the site, change them promptly and monitor the accounts for unauthorized activity. Defenders should block traffic to x-pay.help, add the domain to threat‑intel feeds, and continue to watch for any future changes.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-26T16:30:48Z)URLScan screenshot (2026-10-23T07:55:44Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 0 / 92 9 sources

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

88510367-6f11-491d-b8a4-28465d047642

Final URL

https://x-pay.help/

HTTP response

200

Navigation history

  • URL
    https://x-pay.help/
    Status
    200

DOM structure hash

ef44b577413e567695f6c59d553ecc29e09d5bec7428df5468aeb86758dc8358

Document hash

8ace985fdbb870cdb3ffbcb7033dbb3651252ca0b44bf625d182e5dc09efd389

Phishing classifier result

  • phishing

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • New Domains

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    api.x-pay.help
    Type
    A
    Value
    172.67.187.76
  • Name
    api.x-pay.help
    Type
    A
    Value
    104.21.80.228
  • Name
    api.x-pay.help
    Type
    AAAA
    Value
    2606:4700:3031::ac43:bb4c
  • Name
    api.x-pay.help
    Type
    AAAA
    Value
    2606:4700:3037::6815:50e4
  • Name
    x-pay.help
    Type
    A
    Value
    104.21.80.228
  • Name
    x-pay.help
    Type
    A
    Value
    172.67.187.76
  • Name
    x-pay.help
    Type
    AAAA
    Value
    2606:4700:3037::6815:50e4
  • Name
    x-pay.help
    Type
    AAAA
    Value
    2606:4700:3031::ac43:bb4c

DNSSEC valid

No

IP address

104.21.80.228

Registration record

Registrar
Gname.com Pte. Ltd.
Registered
Expires
Nameservers
  • amy.ns.cloudflare.com
  • cleo.ns.cloudflare.com
Original source fields · JSON
Uuid
88510367-6f11-491d-b8a4-28465d047642
Final url
https://x-pay.help/
Status
200
History
[
    {
        "url": "https://x-pay.help/",
        "status": 200
    }
]
DOM structure hash
ef44b577413e567695f6c59d553ecc29e09d5bec7428df5468aeb86758dc8358
Document hash
8ace985fdbb870cdb3ffbcb7033dbb3651252ca0b44bf625d182e5dc09efd389
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "api.x-pay.help",
        "type": "A",
        "value": "172.67.187.76"
    },
    {
        "name": "api.x-pay.help",
        "type": "A",
        "value": "104.21.80.228"
    },
    {
        "name": "api.x-pay.help",
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:bb4c"
    },
    {
        "name": "api.x-pay.help",
        "type": "AAAA",
        "value": "2606:4700:3037::6815:50e4"
    },
    {
        "name": "x-pay.help",
        "type": "A",
        "value": "104.21.80.228"
    },
    {
        "name": "x-pay.help",
        "type": "A",
        "value": "172.67.187.76"
    },
    {
        "name": "x-pay.help",
        "type": "AAAA",
        "value": "2606:4700:3037::6815:50e4"
    },
    {
        "name": "x-pay.help",
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:bb4c"
    }
]
Dnssec valid
false
Ip
104.21.80.228
Registration record
{
    "registrar": "Gname.com Pte. Ltd.",
    "created": "2026-10-20T01:31:50Z",
    "expires": "2027-10-20T23:59:59Z",
    "nameservers": [
        "amy.ns.cloudflare.com",
        "cleo.ns.cloudflare.com"
    ]
}
Separate stored summary: suspicious · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
suspicious
categories
["New Domains","Security Risks"]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

URLScan

Malicious · engine verdict · score 97

SHA-256 8ace985fdbb870cdb3ffbcb7033dbb3651252ca0b44bf625d182e5dc09efd389

Open report
URLScanOriginal source recordObserved: 24 fields

Observed: · Retrieved:

Report ID

01a17911-8cb1-721d-92a3-904393a5870e

Final URL

https://x-pay.help/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://x-pay.help/
    From
    http://x-pay.help/
    Status
    307

IP address

172.64.80.1

Contacted domains

  • api.x-pay.help
  • plugin-code.salesmartly.com
  • bin.bnbstatic.com
  • msg.salesmartly.com
  • srz.salesmartly.com
  • newbasset.s3.ap-east-1.amazonaws.com
  • widget.salesmartly.com
  • client.salesmartly.com
  • api.salesmartly.com
  • mix-ads.oss-accelerate.aliyuncs.com
  • static.cloudflareinsights.com

Contacted IP addresses

  • 47.89.140.29
  • 104.18.23.242
  • 104.18.22.242
  • 3.171.139.89
  • 13.226.94.38
  • 3.5.214.180
  • 52.85.61.56
  • 172.67.187.76
  • 104.16.80.73
  • 172.64.80.1

Autonomous systems (ASN)

  • 45102
  • 13335
  • 16509

Server countries

  • US
  • HK

Linked domains

  • www.tradingview.com

Document hash

8ace985fdbb870cdb3ffbcb7033dbb3651252ca0b44bf625d182e5dc09efd389

Script hashes

  • cb0c6c9f1771d252eee7caa043bdd7cfffbd52c2cc4b18b7be7c4554ed069151
  • 62414303dc3caba3e1b6c53714fe79a1ea719d2785441992e54bd9ef8b163e86
  • 5e545c3087378bfa53bbeadbf9178acb2d011d8f1e303c855eba0769c570ad54
  • de24d01af18e56461133a28c1f19bcd3c242ea7296ff07b722ad6d6fb5dea7bb
  • 2ad3e0af83059e4173a388928d315482fdf9556bdf0b20d81f6f3cf67eb7067a
  • 29de6181f13154b62743ed52e7a928db4ff877d52e5cf41373d8f4e815ed457b
  • 8685dd592194f86822a10bc2cd8d6f397d9eadd116d1630739f1f908a29cf02b
  • 96d2749a39b4d6abf12f0448e67a30ad897c62c0ee79455cb8016ef3ed7ef271

JavaScript globals

  • TradingView
  • __ACChat
  • addMeta
  • lib
  • rem
  • dpr
  • __VUE_INSTANCE_SETTERS__
  • __INTLIFY_PROD_DEVTOOLS__
  • __INTLIFY_JIT_COMPILATION__
  • __INTLIFY_DROP_MESSAGE_COMPILER__
  • __VUE_I18N_FULL_INSTALL__
  • __VUE_I18N_LEGACY_API__
  • PubSub
  • setImmediate
  • clearImmediate
  • litPropertyMetadata
  • reactiveElementVersions
  • litHtmlVersions
  • litElementVersions
  • __config
  • __theme
  • apiready
  • __VUE__
  • __cfBeacon
  • __ssc
  • ssq
  • install_ss_chat_plugin
  • ss_chat_plugin_version
  • __read
  • __spreadArray
  • __SS_CHAT_RUNTIME__
  • __SS_CHAT_SCRIPT_MODE__
  • SHOPINFO
  • ASSETS_HOSTNAME_VARIABLE
  • ASSETS_CDN_HOSTNAME_VARIABLE
  • STATIC_HOSTNAME_VARIABLE
  • __SS_CHAT_SHADOWROOT__
  • ssmEvent
  • __VUE_SSR_SETTERS__
  • saveAs

Cookies

  • ss_uid
  • _ss_s_uid

Browser storage keys

  • DERIVA_THEME
  • main
  • DERIVA_LANGUAGE
  • salesmartly_p_g1kwgl3_session_tab_key
  • salesmartly_p_g1kwgl3_u_i
  • salesmartly_p_g1kwgl3_custom_fields_local_map
  • salesmartly_p_g1kwgl3_p_xma_
  • salesmartly_p_g1kwgl3_g_uid
  • salesmartly_p_g1kwgl3_token_date
  • salesmartly_p_g1kwgl3_token
  • ss_p_c_l_v_pro
  • salesmartly_p_g1kwgl3_n_u

TLS session and certificate

Subject alternative names
  • *.x-pay.help
  • x-pay.help
Cipher
AES_128_GCM
Issuer
YE2
Subject
x-pay.help
Protocol
QUIC
Valid until
Valid from

Domain age, days

5

Registered domain age, days

5

Certificate age, days

6

Certificate validity, days

89

Page requests

107

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html
Original source fields · JSON
Uuid
01a17911-8cb1-721d-92a3-904393a5870e
Final url
https://x-pay.help/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://x-pay.help/",
        "from": "http://x-pay.help/",
        "status": 307
    }
]
Ip
172.64.80.1
Contacted domains
[
    "api.x-pay.help",
    "plugin-code.salesmartly.com",
    "bin.bnbstatic.com",
    "msg.salesmartly.com",
    "srz.salesmartly.com",
    "newbasset.s3.ap-east-1.amazonaws.com",
    "widget.salesmartly.com",
    "client.salesmartly.com",
    "api.salesmartly.com",
    "mix-ads.oss-accelerate.aliyuncs.com",
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "47.89.140.29",
    "104.18.23.242",
    "104.18.22.242",
    "3.171.139.89",
    "13.226.94.38",
    "3.5.214.180",
    "52.85.61.56",
    "172.67.187.76",
    "104.16.80.73",
    "172.64.80.1"
]
Asns
[
    "45102",
    "13335",
    "16509"
]
Countries
[
    "US",
    "HK"
]
Linked domains
[
    "www.tradingview.com"
]
Document hash
8ace985fdbb870cdb3ffbcb7033dbb3651252ca0b44bf625d182e5dc09efd389
Script hashes
[
    "cb0c6c9f1771d252eee7caa043bdd7cfffbd52c2cc4b18b7be7c4554ed069151",
    "62414303dc3caba3e1b6c53714fe79a1ea719d2785441992e54bd9ef8b163e86",
    "5e545c3087378bfa53bbeadbf9178acb2d011d8f1e303c855eba0769c570ad54",
    "de24d01af18e56461133a28c1f19bcd3c242ea7296ff07b722ad6d6fb5dea7bb",
    "2ad3e0af83059e4173a388928d315482fdf9556bdf0b20d81f6f3cf67eb7067a",
    "29de6181f13154b62743ed52e7a928db4ff877d52e5cf41373d8f4e815ed457b",
    "8685dd592194f86822a10bc2cd8d6f397d9eadd116d1630739f1f908a29cf02b",
    "96d2749a39b4d6abf12f0448e67a30ad897c62c0ee79455cb8016ef3ed7ef271"
]
Globals
[
    "TradingView",
    "__ACChat",
    "addMeta",
    "lib",
    "rem",
    "dpr",
    "__VUE_INSTANCE_SETTERS__",
    "__INTLIFY_PROD_DEVTOOLS__",
    "__INTLIFY_JIT_COMPILATION__",
    "__INTLIFY_DROP_MESSAGE_COMPILER__",
    "__VUE_I18N_FULL_INSTALL__",
    "__VUE_I18N_LEGACY_API__",
    "PubSub",
    "setImmediate",
    "clearImmediate",
    "litPropertyMetadata",
    "reactiveElementVersions",
    "litHtmlVersions",
    "litElementVersions",
    "__config",
    "__theme",
    "apiready",
    "__VUE__",
    "__cfBeacon",
    "__ssc",
    "ssq",
    "install_ss_chat_plugin",
    "ss_chat_plugin_version",
    "__read",
    "__spreadArray",
    "__SS_CHAT_RUNTIME__",
    "__SS_CHAT_SCRIPT_MODE__",
    "SHOPINFO",
    "ASSETS_HOSTNAME_VARIABLE",
    "ASSETS_CDN_HOSTNAME_VARIABLE",
    "STATIC_HOSTNAME_VARIABLE",
    "__SS_CHAT_SHADOWROOT__",
    "ssmEvent",
    "__VUE_SSR_SETTERS__",
    "saveAs"
]
Cookies
[
    "ss_uid",
    "_ss_s_uid"
]
Storage keys
[
    "DERIVA_THEME",
    "main",
    "DERIVA_LANGUAGE",
    "salesmartly_p_g1kwgl3_session_tab_key",
    "salesmartly_p_g1kwgl3_u_i",
    "salesmartly_p_g1kwgl3_custom_fields_local_map",
    "salesmartly_p_g1kwgl3_p_xma_",
    "salesmartly_p_g1kwgl3_g_uid",
    "salesmartly_p_g1kwgl3_token_date",
    "salesmartly_p_g1kwgl3_token",
    "ss_p_c_l_v_pro",
    "salesmartly_p_g1kwgl3_n_u"
]
Tls
{
    "san": [
        "*.x-pay.help",
        "x-pay.help"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "x-pay.help",
    "protocol": "QUIC",
    "valid_to": "2027-01-18T00:46:38Z",
    "valid_from": "2026-10-20T00:46:39Z"
}
Domain age days
5
Apex age days
5
Tls age days
6
Tls valid days
89
Requests
107
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
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
01a167d0-a7f9-7260-8b82-3e79504c86aa
score
null
malicious
null
result_at
null
enriched_at
2026-10-27T09:20:14Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-27 10:20:14"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 7 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
0
Suspicious
0
Undetected
39

Reputation score

0

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3037::6815:50e4
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.187.76
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3031::ac43:bb4c
  • TTL, seconds
    21600
    Type
    NS
    Value
    cleo.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    amy.ns.cloudflare.com
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    amy.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.80.228

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.x-pay.help
  • x-pay.help
Issuer
Let's Encrypt / YE2
Serial
52e53d2078785104a5e3363672b4f3e0fea
SHA-256
b56c889d15a2b56d2489e32e9dc2b49481db722c2a148f9dd2518a0dbb098972
Subject
x-pay.help
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 39
}
Reputation
0
First seen
2026-10-20T02:25:04Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::6815:50e4"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.187.76"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:bb4c"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "cleo.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "amy.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "amy.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.80.228"
    }
]
Dns at
2026-10-21T08:48:49Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.x-pay.help",
        "x-pay.help"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "52e53d2078785104a5e3363672b4f3e0fea",
    "sha256": "b56c889d15a2b56d2489e32e9dc2b49481db722c2a148f9dd2518a0dbb098972",
    "subject": "x-pay.help",
    "valid_to": "2027-01-18T00:46:38Z",
    "valid_from": "2026-10-20T00:46:39Z"
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-21 08:48:33 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-21T08:48:33Z
fetched_at
2026-10-26T16:28:06Z
stats
{"timeout":0,"harmless":53,"malicious":0,"suspicious":0,"undetected":39}

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report

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
x-pay.help — Suspicious Domain
ai_description
PhishDestroy flagged x-pay.help, which shows the title “Xpay”, as suspicious seen on 2026-10-26; VirusTotal and Google Safe Browsing show no detections.
ai_generated_at
2026-10-26T16:39:03Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider 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
Website checksOriginal source recordRetrieved: 23 fields

Mail configuration

SPF lookups
0

CAA records

Domain
x-pay.help

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
2716

Page title and metadata

Page title
Xpay
Open Graph image
/platform/deriva/logo_144.png?2.0.1793017321335
Open Graph title
Xpay
Keywords
Xpay
Theme color
#ffffff
Description
Xpay
Open Graph description
Xpay

Trackers

Requests
77
Observed services
  • Name
    Amazon Web Services
    Company
    Amazon
    Country
    US
    Category
    Hosting
    Requests
    4

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
97
Waiting
475
Connection
6
Download
0
Response time, ms
580

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
4115
CO₂, grams
0.0002
Cleaner than, %
91

DNS servers

Nameservers
  • IP address
    173.245.59.89
    Host
    cleo.ns.cloudflare.com
  • IP address
    172.64.32.101
    Host
    amy.ns.cloudflare.com
DNS zone
x-pay.help

Location

IP address
2606:4700:3031::ac43:bb4c
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
x-pay.help

DNS records

A
  • 104.21.80.228
  • 172.67.187.76
NS
  • amy.ns.cloudflare.com
  • cleo.ns.cloudflare.com
SOA
Primary nameserver
amy.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418104345
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3037::6815:50e4
  • 2606:4700:3031::ac43:bb4c

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
2606:4700:3031::ac43:bb4c
IP version
6

Redirects

Redirect chain
  • https://x-pay.help

Registration record

Registrar
Gname.com Pte. Ltd.
Registered
Updated
Expires
Status
  • serverTransferProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • amy.ns.cloudflare.com
  • cleo.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "x-pay.help"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-26T16:29:32Z",
    "first": "2026-10-26T16:29:32Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 2716
}
Page title and metadata
{
    "title": "Xpay",
    "ogImage": "/platform/deriva/logo_144.png?2.0.1793017321335",
    "ogTitle": "Xpay",
    "keywords": "Xpay",
    "themeColor": "#ffffff",
    "description": "Xpay",
    "ogDescription": "Xpay"
}
Trackers
{
    "requests": 77,
    "trackers": [
        {
            "name": "Amazon Web Services",
            "company": "Amazon",
            "country": "US",
            "category": "Hosting",
            "requests": 4
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 97,
        "wait": 475,
        "connect": 6,
        "download": 0
    },
    "response_ms": 580
}
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
    ]
}
Carbon
{
    "bytes": 4115,
    "co2_grams": 0.0002,
    "cleaner_than": 91
}
Dns server
{
    "ns": [
        {
            "ip": "173.245.59.89",
            "host": "cleo.ns.cloudflare.com"
        },
        {
            "ip": "172.64.32.101",
            "host": "amy.ns.cloudflare.com"
        }
    ],
    "zone": "x-pay.help"
}
Location
{
    "ip": "2606:4700:3031::ac43:bb4c",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "x-pay.help"
}
DNS records
{
    "A": [
        "104.21.80.228",
        "172.67.187.76"
    ],
    "NS": [
        "amy.ns.cloudflare.com",
        "cleo.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"amy.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418104345, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:3037::6815:50e4",
        "2606:4700:3031::ac43:bb4c"
    ]
}
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": "2606:4700:3031::ac43:bb4c",
    "family": 6
}
Redirects
{
    "chain": [
        "https://x-pay.help"
    ]
}
Registration record
{
    "registrar": "Gname.com Pte. Ltd.",
    "created": "2026-10-20T01:31:50Z",
    "updated": "2026-10-25T01:35:10Z",
    "expires": "2027-10-20T23:59:59Z",
    "status": [
        "serverTransferProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "amy.ns.cloudflare.com",
        "cleo.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html"
    }
}

Questions about x-pay.help

Is x-pay.help legit?

No. PhishDestroy classifies x-pay.help as a blocklisted domain (risk: critical, 75/100); it was first detected on 2026-10-26. Treat the site as unsafe.

Is x-pay.help safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on x-pay.help. 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 x-pay.help?

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 matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 7 captures

Primary capture 1 / 7
SourcePrimary capture
Recorded
StateStored capture
HTTP status200
Final URLhttps://x-pay.help/
Position1 / 7
Open capture Wayback Download
All capture links and hashes (7)
Observed page title
Xpay
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 81 days
x-pay.help: Crypto scam — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 75/100 (critical).
Social preview card x-pay.help: Crypto scam — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 75/100 (critical). v acee70f9d708

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 97 report ↗
IP Context Canada172.67.187.76 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Gname SG(SG)
Abuse contactcomplaint@gname.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for x-pay.help →
RegistrationCreated Oct 20, 2026 (8d · Very New!) — Expires Oct 20, 2027
WHOIS statusserverTransferProhibitedclientTransferProhibited
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 75/100
Submitted URLhttp://x-pay.help/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.67.187.76
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

  • amy.ns.cloudflare.com
  • cleo.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-20 00:46:39
Valid until
2027-01-18 00:46:38
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintb56c889d15a2b56d2489e32e9dc2b49481db722c2a148f9dd2518a0dbb098972
Certificate names · 2 SANs
  • *.x-pay.help
  • x-pay.help

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

viewdns.info · 172.67.187.76rapiddns.io

Latest Classified Outcome 2026-10-27 23:04:22 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unknown Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-27 23:04:22 UTC
RDAP registration
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 · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of x-pay.help · checked Oct 26, 2026

47
Poor
Performance
FCP
8.2 s
First Contentful Paint
LCP
15.07 s
Largest Contentful Paint
CLS
0.17
Cumulative Layout Shift
TBT
82 ms
Total Blocking Time
SI
14.06 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: http://x-pay.help/
Final URL: https://x-pay.help/
Xpay
Xpay
Response
HTTP 200
HTML body
4.0 KB
Compressed
1.4 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: Xpay
Open Graph description: Xpay
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a50ad32abf40b18f-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Mon, 26 Oct 2026 16:26:49 GMT
Last-Modified
Mon, 26 Oct 2026 12:22:01 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=LiYToK4y1XTXCbBwVwN4yLY%2Fy2hAxmKoHefkuMkqy8fTKj2FCG%2BIKaUg5dieOw7Z0cvT3y1Kg0DV53xR40HMCt%2FznE4iL0MwIzzx6anq0dG5WGmeqG1uMap9uV4B"}]}
Server
cloudflare
Transfer-Encoding
chunked
Vary
accept-encoding

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

Archived
Stored observation history2

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

    live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability observations7

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_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:04:22.000000
    Evidence SHA-256
    ad64cceb02833786d732cba3e99c7e05f3578582ddb427c42a916ebb8a99b508
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:04:22
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:04:22.000000
    Evidence SHA-256
    ad64cceb02833786d732cba3e99c7e05f3578582ddb427c42a916ebb8a99b508
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:04:22
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:04:23.000000
    Evidence SHA-256
    e786ff5f27d39cc6ddf395fca49a1e8b02289c02c83a0e25d9ca35fcbe507dc4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:04:23
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:04:23.000000
    Evidence SHA-256
    e786ff5f27d39cc6ddf395fca49a1e8b02289c02c83a0e25d9ca35fcbe507dc4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:04:23
    Evidence reason
    alive_content
  5. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 17:37:57.000000
    Evidence SHA-256
    39b60c4dceb49e7b86d6ae67a60a3cb85673da804764e42ad30959cc36cf0569
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 17:37:57
    Evidence reason
  6. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 17:37:57.000000
    Evidence SHA-256
    39b60c4dceb49e7b86d6ae67a60a3cb85673da804764e42ad30959cc36cf0569
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 17:37:57
    Evidence reason
  7. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 17:30:33.538661
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 9. 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
    x-pay.help detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Blocklist Detection · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 97
  • 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.
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Gname.com Pte. Ltd.. Abuse contacts: 1.
    • complaint@gname.com
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. Abuse report sent

    PD-20261026-7AF4AA · Receipt 83486

    complaint@gname.com
  2. URLScan

    Page captured

    View source
  3. Cloudflare Radar

    Phishing

    View source
  4. VirusTotal

    0/92 engine detections

    View source
  5. Added to PhishDestroy

    x-pay.help

    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

Check for cloaking

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

x-pay.help

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261026-7AF4AA Recipient: complaint@gname.com
PDF notice generated Notice text archived (317 characters)
Abuse notice text as sent to the provider 
Registrar: Gname.com Pte. Ltd. (Singapore)
Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain
Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
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 1 stored notification records Last known active
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.

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

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • 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 x-pay.help)
  • 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.

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.

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/x-pay.help"
  title="PhishDestroy threat report for x-pay.help"
  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>