Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 4/92 engines flagged. malicious: 2. suspicious: 2. Analysis time (as stored): 2026-11-05T01:27:00Z. Retrieved (as stored): 2026-11-05T03:38:53Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
boc.wallet-payment.cc favicon

boc.wallet-payment.cc

In short

PhishDestroy first recorded boc.wallet-payment.cc on 2026-11-05. Stored VirusTotal result: 4/92 engines flagged. malicious: 2. suspicious: 2. Analysis time (as stored): 2026-11-05T01:27:00Z. Retrieved (as stored): 2026-11-05T03:38:53Z.

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Canada172.67.168.216Cloudflare, Inc. · CDN
Registered
Jul 30, 2026
First observed
Nov 5, 2026
PhishDestroy assessment Critical
72/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 4/92 Spamhaus DBL: phishing domain
VirusTotal
4 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 97
Cloudflare Radar
Phishing
Page captures
3
open gallery
Domain age
97 days
registered 2026-07-30 according to WHOIS · source data differ
Nov 5, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded boc.wallet-payment.cc on 2026-11-05. Stored VirusTotal result: 4/92 engines flagged. malicious: 2. suspicious: 2. Analysis time (as stored): 2026-11-05T01:27:00Z. Retrieved (as stored): 2026-11-05T03:38:53Z. Risk: critical (72/100). Registrar: Dynadot. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
4 / 92
Hosting
Canada172.67.168.216Cloudflare, Inc. · CDN
Registrar
United StatesDynadot
Registered
Jul 30, 2026
Page captures
3
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for boc.wallet-payment.cc. 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 4 / 92 7 sources

VirusTotal

4 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
2
Suspicious
2
Undetected
35

Vendor labels

CRDF
malicious
Fortinet
spam
alphaMountain.ai
spam
Forcepoint ThreatSeeker
malicious

Reputation score

0

Registrar

Dynadot Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    172.67.168.216
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3037::6815:26f4
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.38.244
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3035::ac43:a8d8

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • wallet-payment.cc
  • *.wallet-payment.cc
Issuer
Google Trust Services / WE1
Serial
ea7dde4d47386c1813d1e6e26642a4a6
SHA-256
5afa0380c4c65b9f97cfb4dd9fdc0a5b2c638cb18ec0981b4cb1da64b44cadfa
Subject
wallet-payment.cc
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
  • autumn.ns.cloudflare.com
  • donovan.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 2,
    "suspicious": 2,
    "undetected": 35
}
Vendor labels
{
    "CRDF": "malicious",
    "Fortinet": "spam",
    "alphaMountain.ai": "spam",
    "Forcepoint ThreatSeeker": "malicious"
}
Reputation
0
Registrar
Dynadot Inc
Created
2026-07-30T06:35:45Z
Expires
2027-07-30T06:35:45Z
Updated
2026-07-30T07:00:09Z
First seen
2026-11-05T01:27:14Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.168.216"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::6815:26f4"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.38.244"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3035::ac43:a8d8"
    }
]
Dns at
2026-11-05T01:27:16Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "wallet-payment.cc",
        "*.wallet-payment.cc"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "ea7dde4d47386c1813d1e6e26642a4a6",
    "sha256": "5afa0380c4c65b9f97cfb4dd9fdc0a5b2c638cb18ec0981b4cb1da64b44cadfa",
    "subject": "wallet-payment.cc",
    "valid_to": "2026-12-26T09:29:13Z",
    "valid_from": "2026-09-27T08:30:38Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-07-30T06:35:45Z",
    "updated": "2026-07-30T07:00:09Z",
    "expires": "2027-07-30T06:35:45Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "autumn.ns.cloudflare.com",
        "donovan.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
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
4
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","CRDF","Forcepoint ThreatSeeker","Fortinet"]
observed_at
2026-11-05 01:27:00
checked_at
2026-11-05 04:38:53
fetched_at
2026-11-05 03:38:54
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

6dac18b5-7242-4fc7-ac31-1d309dbca99b

Final URL

https://boc.wallet-payment.cc/

HTTP response

200

Navigation history

  • URL
    https://boc.wallet-payment.cc/
    Status
    200

DOM structure hash

35825c6c458364f7237a4618e9d9348088b902cfdc6ab05284b1186ca74f50b4

Document hash

4f0a25c79be603f86e789c8d86ead7bb57187b052b4c04182e48884cbc9052fd

Phishing classifier result

  • phishing

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    boc.wallet-payment.cc
    Type
    A
    Value
    172.67.168.216
  • Name
    boc.wallet-payment.cc
    Type
    A
    Value
    104.21.38.244
  • Name
    boc.wallet-payment.cc
    Type
    AAAA
    Value
    2606:4700:3037::6815:26f4
  • Name
    boc.wallet-payment.cc
    Type
    AAAA
    Value
    2606:4700:3035::ac43:a8d8

DNSSEC valid

No

IP address

127.0.1.14

127.0.1.14 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Nameservers
  • autumn.ns.cloudflare.com
  • donovan.ns.cloudflare.com
Original source fields · JSON
Uuid
6dac18b5-7242-4fc7-ac31-1d309dbca99b
Final url
https://boc.wallet-payment.cc/
Status
200
History
[
    {
        "url": "https://boc.wallet-payment.cc/",
        "status": 200
    }
]
DOM structure hash
35825c6c458364f7237a4618e9d9348088b902cfdc6ab05284b1186ca74f50b4
Document hash
4f0a25c79be603f86e789c8d86ead7bb57187b052b4c04182e48884cbc9052fd
Phishing v2
[
    "phishing"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "boc.wallet-payment.cc",
        "type": "A",
        "value": "172.67.168.216"
    },
    {
        "name": "boc.wallet-payment.cc",
        "type": "A",
        "value": "104.21.38.244"
    },
    {
        "name": "boc.wallet-payment.cc",
        "type": "AAAA",
        "value": "2606:4700:3037::6815:26f4"
    },
    {
        "name": "boc.wallet-payment.cc",
        "type": "AAAA",
        "value": "2606:4700:3035::ac43:a8d8"
    }
]
Dnssec valid
false
Ip
127.0.1.14

127.0.1.14 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-07-30T06:35:45Z",
    "updated": "2026-07-30T07:00:09Z",
    "expires": "2027-07-30T06:35:45Z",
    "nameservers": [
        "autumn.ns.cloudflare.com",
        "donovan.ns.cloudflare.com"
    ]
}
Separate stored summary: Not recorded · 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
null
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 97

SHA-256 eb5558546012cced2773edd4262d13e5d72d4336b8ec6f0d1a3aa972b6b9538f

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a1a951-0695-7088-b214-ab9004f954dc

Final URL

https://boc.wallet-payment.cc/

HTTP response

200

IP address

104.21.38.244

Contacted domains

  • centervmitalk.cc
  • dgklfruc8h4ce.cloudfront.net
  • fonts.gstatic.com
  • fonts.googleapis.com
  • js

Contacted IP addresses

  • 54.192.87.78
  • 142.251.14.94
  • 142.251.20.95
  • 188.114.96.3
  • 188.114.97.3
  • 104.21.38.244

Autonomous systems (ASN)

  • 16509
  • 15169
  • 13335

Server countries

  • US

Document hash

eb5558546012cced2773edd4262d13e5d72d4336b8ec6f0d1a3aa972b6b9538f

Script hashes

  • 523555df17a57138f1e69d3653ebcb6fa2e4c12f9e7b26ee7c766136df3bf6be
  • 66507d5d502c508d4898c9c7ad8764423bee62900ae51e6c1af149319fa9c3ee
  • 48b453ff001cc3857fafe21cf3c149500af787798fc2a6f98cdaddb2ec5e33ea
  • f5fbbbfc3bd3a8f9269e43dd0ffcef721f60be7e79a8f25343b59df346e774d8
  • f324501a3dafb3db6a4a593009866d5c1a80b17532a1bc021fcad5af48c4d6ac
  • 386b8756f26ca1f1ccacdda2b924810db70be3d6b60f29f8a6108046d61b559d
  • e59a8c7b123a71bbe271d02c822790617e14e8961e527b950fef71d20df8e2ce

JavaScript globals

  • $
  • jQuery
  • langUrl
  • langMbk
  • extSysIsShowTNPS
  • isEnglishNumber
  • isAddressCheck
  • isAddressPreApproval
  • isMBKAddressPreApproval
  • isNumber
  • isNumberCommas
  • isEnglish
  • isAllZero
  • alertBox1
  • alertBox2
  • alertBox3
  • goToMinisite2
  • openCallDialog
  • closeCallDialog
  • addCommas
  • isValidDate
  • calculationAge
  • IsHKID
  • checkRadioValue
  • getCheckedRadioValue
  • setRadioValue
  • gen2Years
  • gen2Months
  • goTel
  • goDocument
  • containNotAllowedChar
  • extSysReturnResult
  • callMbk
  • extSysKeepSession
  • extSysClosePage
  • extSysOpenPdfFile
  • extSysOpenHtml
  • extSysShowOverlay
  • extSysCallAppMotion
  • extSysCreateIADSConsent

Browser storage keys

  • CHAT_WIDGET_V2_RUNTIME_STATUS
  • pdfjs.history
  • chat_visitor_link_9ef10dd95fe6cb7870629b88b7c10039_anon

TLS session and certificate

Subject alternative names
  • wallet-payment.cc
  • *.wallet-payment.cc
Cipher
AES_128_GCM
Issuer
WE1
Subject
wallet-payment.cc
Protocol
QUIC
Valid until
Valid from

Domain age, days

0

Differs from the registration date in WHOIS (2026-07-30), which gives 97 days on the scan date 2026-11-05. The two sources disagree; both values are kept as recorded.

Registered domain age, days

97

Certificate age, days

38

Certificate validity, days

90

Page requests

53

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
97
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html
Priority
u=0,i
Original source fields · JSON
Uuid
01a1a951-0695-7088-b214-ab9004f954dc
Final url
https://boc.wallet-payment.cc/
Status
200
Ip
104.21.38.244
Contacted domains
[
    "centervmitalk.cc",
    "dgklfruc8h4ce.cloudfront.net",
    "fonts.gstatic.com",
    "fonts.googleapis.com",
    "js"
]
Contacted IP addresses
[
    "54.192.87.78",
    "142.251.14.94",
    "142.251.20.95",
    "188.114.96.3",
    "188.114.97.3",
    "104.21.38.244"
]
Asns
[
    "16509",
    "15169",
    "13335"
]
Countries
[
    "US"
]
Document hash
eb5558546012cced2773edd4262d13e5d72d4336b8ec6f0d1a3aa972b6b9538f
Script hashes
[
    "523555df17a57138f1e69d3653ebcb6fa2e4c12f9e7b26ee7c766136df3bf6be",
    "66507d5d502c508d4898c9c7ad8764423bee62900ae51e6c1af149319fa9c3ee",
    "48b453ff001cc3857fafe21cf3c149500af787798fc2a6f98cdaddb2ec5e33ea",
    "f5fbbbfc3bd3a8f9269e43dd0ffcef721f60be7e79a8f25343b59df346e774d8",
    "f324501a3dafb3db6a4a593009866d5c1a80b17532a1bc021fcad5af48c4d6ac",
    "386b8756f26ca1f1ccacdda2b924810db70be3d6b60f29f8a6108046d61b559d",
    "e59a8c7b123a71bbe271d02c822790617e14e8961e527b950fef71d20df8e2ce"
]
Globals
[
    "$",
    "jQuery",
    "langUrl",
    "langMbk",
    "extSysIsShowTNPS",
    "isEnglishNumber",
    "isAddressCheck",
    "isAddressPreApproval",
    "isMBKAddressPreApproval",
    "isNumber",
    "isNumberCommas",
    "isEnglish",
    "isAllZero",
    "alertBox1",
    "alertBox2",
    "alertBox3",
    "goToMinisite2",
    "openCallDialog",
    "closeCallDialog",
    "addCommas",
    "isValidDate",
    "calculationAge",
    "IsHKID",
    "checkRadioValue",
    "getCheckedRadioValue",
    "setRadioValue",
    "gen2Years",
    "gen2Months",
    "goTel",
    "goDocument",
    "containNotAllowedChar",
    "extSysReturnResult",
    "callMbk",
    "extSysKeepSession",
    "extSysClosePage",
    "extSysOpenPdfFile",
    "extSysOpenHtml",
    "extSysShowOverlay",
    "extSysCallAppMotion",
    "extSysCreateIADSConsent"
]
Storage keys
[
    "CHAT_WIDGET_V2_RUNTIME_STATUS",
    "pdfjs.history",
    "chat_visitor_link_9ef10dd95fe6cb7870629b88b7c10039_anon"
]
Tls
{
    "san": [
        "wallet-payment.cc",
        "*.wallet-payment.cc"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "wallet-payment.cc",
    "protocol": "QUIC",
    "valid_to": "2026-12-26T09:29:13Z",
    "valid_from": "2026-09-27T08:30:38Z"
}
Domain age days
0

Differs from the registration date in WHOIS (2026-07-30), which gives 97 days on the scan date 2026-11-05. The two sources disagree; both values are kept as recorded.

Apex age days
97
Tls age days
38
Tls valid days
90
Requests
53
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html",
    "priority": "u=0,i"
}
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
01a1a951-0695-7088-b214-ab9004f954dc
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

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-11-05T03:20:19Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-11-05T03:20:19Z
source_timestamp
2026-11-05 04:20:19
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: 23 fields

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
4555

Crawler rules

User agents
  • *
  • Amazonbot
  • Applebot-Extended
  • Bytespider
  • CCBot
Present
Yes

Trackers

Requests
32

Forms and mixed content

Scripts without SRI
  • https://centervmitalk.cc/agent/embed-v2.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
4
TLS
17
Waiting
630
Connection
8
Download
1
Response time, ms
660

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
8832
CO₂, grams
0.0003
Cleaner than, %
74

DNS servers

Nameservers
  • IP address
    172.64.35.114
    Host
    donovan.ns.cloudflare.com
  • IP address
    162.159.38.148
    Host
    autumn.ns.cloudflare.com
DNS zone
wallet-payment.cc

Location

IP address
2606:4700:3037::6815:26f4
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Google Trust Services / WE1
Subject
wallet-payment.cc

DNS records

A
  • 104.21.38.244
  • 172.67.168.216
AAAA
  • 2606:4700:3037::6815:26f4
  • 2606:4700:3035::ac43:a8d8

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:3037::6815:26f4
IP version
6

Redirects

Redirect chain
  • https://boc.wallet-payment.cc

Technology stack

Technologies
  • Java
  • UIKit
  • JavaServer Faces
  • jQuery
  • Cloudflare
  • HTTP/3

Page links

Internal links
1

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • autumn.ns.cloudflare.com
  • donovan.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html
Original source fields · JSON
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-11-05T01:29:27Z",
    "first": "2026-11-05T01:29:27Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 4555
}
Crawler rules
{
    "agents": [
        "*",
        "Amazonbot",
        "Applebot-Extended",
        "Bytespider",
        "CCBot"
    ],
    "present": true
}
Trackers
{
    "requests": 32
}
Forms and mixed content
{
    "no_sri": [
        "https://centervmitalk.cc/agent/embed-v2.js"
    ],
    "third_party_scripts": 1
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 4,
        "tls": 17,
        "wait": 630,
        "connect": 8,
        "download": 1
    },
    "response_ms": 660
}
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": 8832,
    "co2_grams": 0.0003,
    "cleaner_than": 74
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.35.114",
            "host": "donovan.ns.cloudflare.com"
        },
        {
            "ip": "162.159.38.148",
            "host": "autumn.ns.cloudflare.com"
        }
    ],
    "zone": "wallet-payment.cc"
}
Location
{
    "ip": "2606:4700:3037::6815:26f4",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "wallet-payment.cc"
}
DNS records
{
    "A": [
        "104.21.38.244",
        "172.67.168.216"
    ],
    "AAAA": [
        "2606:4700:3037::6815:26f4",
        "2606:4700:3035::ac43:a8d8"
    ]
}
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:3037::6815:26f4",
    "family": 6
}
Redirects
{
    "chain": [
        "https://boc.wallet-payment.cc"
    ]
}
Tech stack
{
    "technologies": [
        "Java",
        "UIKit",
        "JavaServer Faces",
        "jQuery",
        "Cloudflare",
        "HTTP/3"
    ]
}
Page links
{
    "internal_count": 1
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-07-30T06:35:45Z",
    "updated": "2026-07-30T07:00:09Z",
    "expires": "2027-07-30T06:35:45Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "autumn.ns.cloudflare.com",
        "donovan.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html"
    }
}

Questions about boc.wallet-payment.cc

Is boc.wallet-payment.cc legit?

PhishDestroy rates boc.wallet-payment.cc as critical risk (72/100) from the recorded evidence; it was first recorded on 2026-11-05. Stored VirusTotal result: 4/92 engines flagged. malicious: 2. suspicious: 2. Analysis time (as stored): 2026-11-05T01:27:00Z. Retrieved (as stored): 2026-11-05T03:38:53Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is boc.wallet-payment.cc safe to connect a wallet?

This report does not record which wallet requests boc.wallet-payment.cc 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 boc.wallet-payment.cc?

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 · 3 captures

URLScan · 2026-11-05 1 / 3
SourceURLScan · 2026-11-05
Recorded
StateStored capture
HTTP status200
Final URLhttps://boc.wallet-payment.cc/
Position1 / 3
Open capture Source Report Wayback Download
All capture links and hashes (3)

Domain details

Domain
IP Context Canada172.67.168.216 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Dynadot US(US)
Abuse contact["abuse@dynadot.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for wallet-payment.cc →
Registration (base domain)wallet-payment.cc · Created Jul 30, 2026 (97d) — Expires Jul 30, 2027
WHOIS statusclientTransferProhibited
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedNov 5, 2026
DOM Analysisanalyzed Nov 5, 2026score 0/100
Submitted URLhttp://boc.wallet-payment.cc/
Favicon Hash
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 51 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • autumn.ns.cloudflare.com
  • donovan.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-27 08:30:38
Valid until
2026-12-26 09:29:13
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint5afa0380c4c65b9f97cfb4dd9fdc0a5b2c638cb18ec0981b4cb1da64b44cadfa
Certificate names · 2 SANs
  • wallet-payment.cc
  • *.wallet-payment.cc

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.168.216rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

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

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of boc.wallet-payment.cc · checked Nov 5, 2026

83
Needs Work
Performance
FCP
2.94 s
First Contentful Paint
LCP
2.94 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
11 ms
Total Blocking Time
SI
7.57 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://boc.wallet-payment.cc/
Final URL: https://boc.wallet-payment.cc/
Response
HTTP 200
HTML body
9.0 KB
Compressed
3.4 KB
Links
1 internal · 0 external
Detected technologies
cloudflarejquery
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
Saved response-header values · 14
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a55815a7cd64aa2d-IAD
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Thu, 05 Nov 2026 01:28:56 GMT
Last-Modified
Sat, 17 Oct 2026 11:53:04 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=H1%2FFV%2F91gwcwPAq%2FB%2FSyRIZrSLeju9wsbGj3OZmmyUcNHlIuciMdOxamEuAqu66CIaBScimuNoF0ftYOKKloukM8wHhgUjeTJdF2byHmamnwW5jwMfl%2BaRclpTflBPn%2FLIR
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

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

Captured network requests

Network requests: 53 SHA-256 hashes: 50 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-05 01:30 UTC.

Open this scan on URLScan 01a1a951-0695-7088-b214-ab9004f954dc ↗

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. VirusTotal · Detection count

    3→4

    Engines added
    CRDF
    Engines removed
    None recorded
    Recorded vendor total
    4
  2. VirusTotal · Detection count

    0→3

    Engines added
    Forcepoint ThreatSeeker · Fortinet · alphaMountain.ai
    Engines removed
    None recorded
    Recorded vendor total
    3
  3. Domain monitor · First collection record

    Reachable

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
    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-11-05 02:29:26.000000
    Evidence SHA-256
    7e94c32567bfd40caab94a83186be394a45fb396842147ba5592aa35f21e68bc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 02:29:26
    Evidence reason
  2. 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-11-05 02:29:26.000000
    Evidence SHA-256
    7e94c32567bfd40caab94a83186be394a45fb396842147ba5592aa35f21e68bc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 02:29:26
    Evidence reason

Threat Response Pipeline

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

Recorded events: 12. 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
    boc.wallet-payment.cc detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded · VirusTotal detections +1 · VirusTotal detections +3 Recorded: 10 of 10
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • 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.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 4/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • VirusTotal detections +1
    New detections: +1 (3 → 4): CRDF
  • VirusTotal detections +3
    New detections: +3 (0 → 3): Forcepoint ThreatSeeker, Fortinet, alphaMountain.ai
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. Cloudflare Radar

    Phishing

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    boc.wallet-payment.cc

    View source
  4. URLScan

    Malicious · engine verdict · score 97

    View source
  5. VirusTotal

    4/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.

boc.wallet-payment.cc

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 4 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report 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?

3 evidence signal groups linked 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.

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 boc.wallet-payment.cc)
  • 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/boc.wallet-payment.cc"
  title="PhishDestroy threat report for boc.wallet-payment.cc"
  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>