Skip to security report
This domain has been flagged as malicious
PhishDestroy forensic analysis flagged this domain. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
bene.finance favicon

bene.finance

In short

PhishDestroy records the bene.finance landing page, where BeneX invites visitors to calculate an amount and submit an exchange request.

“BeneX — обмен криптовалют с ручным сопровождением”

Registrar
RussiaNiceNIC
Resolved IP
Germany103.160.59.100GTHost
Registered
Oct 28, 2026
First observed
Oct 31, 2026
PhishDestroy assessment Medium
25/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Spamhaus DBL: spam domain Young domain: 3 days old
VirusTotal
engine detections ·
OTX
community references
URLScan
engine verdict · score 85
Page captures
open gallery
Domain age
registered 2026-10-28 according to WHOIS · source data differ
OTX: 3 refs Oct 31, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records the bene.finance landing page, where BeneX invites visitors to calculate an amount and submit an exchange request.

Medium
Status
Last known active
VirusTotal
0 / 92
Hosting
Germany103.160.59.100GTHost
Registrar
RussiaNiceNIC
Registered
Oct 28, 2026
OTX
3 community refs
Page captures
5

PhishDestroy analysis, reviewed version

The captured bene.finance page presents BeneX as a cryptocurrency exchange with personal support, headed by "Обмен криптовалют с личным сопровождением." The main interaction is a currency exchange widget labeled "Обмен валют" that currently shows "Загружаем валюты..." and a "Курс по заявке" note, alongside a three-step flow: submit a request, contact the operator in Telegram, and complete the exchange after payment verification. The page also links to exchange guides such as "Как проходит обмен" and network-specific tutorials.

The stored VirusTotal domain result reports 0 detections out of 92 engines.

Source evidenceVirusTotal 0 / 92 · OTX 3 references 8 sources

Spamhaus DBL

spam domain

URLScan

Malicious · engine verdict · score 85

SHA-256 1b5c6925a6b1ff914242737a2350fce75eb7032477363f6b713c8b7fa8c5bd6e

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a19331-ced6-73ea-978e-b758f214af1c

Final URL

https://bene.finance/

HTTP response

200

IP address

103.160.59.100

Reverse DNS (PTR)

server.tsunamix.xyz

Contacted domains

  • api.bene.finance

Contacted IP addresses

  • 103.160.59.100

Autonomous systems (ASN)

  • 63023

Server countries

  • DE

Document hash

1b5c6925a6b1ff914242737a2350fce75eb7032477363f6b713c8b7fa8c5bd6e

Script hashes

  • e6823dfecb57e63fc60a5498d6134868320fad86906e085e74db6c67718bdc8b

JavaScript globals

  • __reactRouterVersion

Browser storage keys

  • tsunamix_language
  • benex_currency_preferences_v1

TLS session and certificate

Subject alternative names
  • admin.bene.finance
  • api.bene.finance
  • bene.finance
Cipher
AES_256_GCM
Issuer
YE1
Subject
bene.finance
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

2950

Differs from the registration date in WHOIS (2026-10-28), which gives 3 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Registered domain age, days

2950

Differs from the registration date in WHOIS (2026-10-28), which gives 3 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Certificate age, days

3

Certificate validity, days

89

Page requests

9

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html
Strict-transport-security
max-age=31536000
Content-security-policy
default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.bene.finance; object-src 'none'; base-uri 'self'; f
X-frame-options
DENY
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Original source fields · JSON
Uuid
01a19331-ced6-73ea-978e-b758f214af1c
Final url
https://bene.finance/
Status
200
Ip
103.160.59.100
Ptr
server.tsunamix.xyz
Contacted domains
[
    "api.bene.finance"
]
Contacted IP addresses
[
    "103.160.59.100"
]
Asns
[
    "63023"
]
Countries
[
    "DE"
]
Document hash
1b5c6925a6b1ff914242737a2350fce75eb7032477363f6b713c8b7fa8c5bd6e
Script hashes
[
    "e6823dfecb57e63fc60a5498d6134868320fad86906e085e74db6c67718bdc8b"
]
Globals
[
    "__reactRouterVersion"
]
Storage keys
[
    "tsunamix_language",
    "benex_currency_preferences_v1"
]
Tls
{
    "san": [
        "admin.bene.finance",
        "api.bene.finance",
        "bene.finance"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YE1",
    "subject": "bene.finance",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-26T10:33:53Z",
    "valid_from": "2026-10-28T10:33:54Z"
}
Domain age days
2950

Differs from the registration date in WHOIS (2026-10-28), which gives 3 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Apex age days
2950

Differs from the registration date in WHOIS (2026-10-28), which gives 3 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Tls age days
3
Tls valid days
89
Requests
9
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 85,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000",
    "content-security-policy": "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.bene.finance; object-src 'none'; base-uri 'self'; f",
    "x-frame-options": "DENY",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin"
}
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
01a19331-ced6-73ea-978e-b758f214af1c
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

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
48
Malicious
0
Suspicious
0
Undetected
44

Reputation score

0

Registrar

GANDI SAS

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    7200
    Type
    A
    Value
    103.160.59.100
  • TTL, seconds
    7200
    Type
    SOA
    Responsible mailbox
    root.bene.finance
    Value
    bene.finance
  • TTL, seconds
    7200
    Type
    NS
    Value
    ns4.my-ndns.com
  • TTL, seconds
    7200
    Type
    NS
    Value
    ns3.my-ndns.com

DNS records observed

JARM fingerprint

28d28d28d00028d00042d42d000000831b6af40378e2dd35eeac4e9311926e

Certificate

Subject alternative names
  • admin.bene.finance
  • api.bene.finance
  • bene.finance
Issuer
Let's Encrypt / YE1
Serial
5de0928307e41a1e59c2396b6bbabae5652
SHA-256
75fe294e282a1f59c920ca718622c97f4ecb4fef4a65f9c90f1a2c290fe24da8
Subject
bene.finance
Valid until
Valid from

Registration record

Registrar
GANDI SAS
Registrar IANA ID
81
Registrar URL
http://www.gandi.net
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • ns-1074.awsdns-06.org
  • ns-1632.awsdns-12.co.uk
  • ns-251.awsdns-31.com
  • ns-862.awsdns-43.net
DNSSEC
Unsigned

Registry data (RDAP)

Status
  • client delete prohibited
  • client transfer prohibited
Registry events
Expiration
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 48,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 44
}
Reputation
0
Registrar
GANDI SAS
Created
2018-09-27T05:25:38Z
Expires
2022-09-27T05:25:38Z
Updated
2021-08-28T20:31:01Z
First seen
2026-10-28T11:36:52Z
DNS records
[
    {
        "ttl": 7200,
        "type": "A",
        "value": "103.160.59.100"
    },
    {
        "ttl": 7200,
        "type": "SOA",
        "rname": "root.bene.finance",
        "value": "bene.finance"
    },
    {
        "ttl": 7200,
        "type": "NS",
        "value": "ns4.my-ndns.com"
    },
    {
        "ttl": 7200,
        "type": "NS",
        "value": "ns3.my-ndns.com"
    }
]
Dns at
2026-10-28T11:41:42Z
Jarm
28d28d28d00028d00042d42d000000831b6af40378e2dd35eeac4e9311926e
Certificate
{
    "san": [
        "admin.bene.finance",
        "api.bene.finance",
        "bene.finance"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "5de0928307e41a1e59c2396b6bbabae5652",
    "sha256": "75fe294e282a1f59c920ca718622c97f4ecb4fef4a65f9c90f1a2c290fe24da8",
    "subject": "bene.finance",
    "valid_to": "2027-01-26T10:33:53Z",
    "valid_from": "2026-10-28T10:33:54Z"
}
Registration record
{
    "registrar": "GANDI SAS",
    "registrar_iana_id": "81",
    "registrar_url": "http://www.gandi.net",
    "created": "2018-09-27T03:25:38Z",
    "updated": "2021-08-23T20:30:19Z",
    "expires": "2022-09-27T05:25:38Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns-1074.awsdns-06.org",
        "ns-1632.awsdns-12.co.uk",
        "ns-251.awsdns-31.com",
        "ns-862.awsdns-43.net"
    ],
    "dnssec": "Unsigned"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-27T16:00:00Z",
        "registration": "2026-10-27T16:00:00Z",
        "registrar expiration": "2027-10-27T16:00:00Z",
        "last update of RDAP database": "2026-10-28T11:41:41Z"
    }
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-28 11:36:54 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-28T11:36:54Z
fetched_at
2026-10-31T18:54:10Z
stats
{"timeout":0,"harmless":48,"malicious":0,"suspicious":0,"undetected":44}

OTX

3 community references

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

5414c833-f551-4148-a045-404878d6eba5

Final URL

https://bene.finance/

HTTP response

200

Navigation history

  • URL
    https://bene.finance/
    Status
    200

DOM structure hash

bbafe2ccc151325cd1582c38200dc9a20506e956fdd4d5d1d21a1d184e77d813

Document hash

1b5c6925a6b1ff914242737a2350fce75eb7032477363f6b713c8b7fa8c5bd6e

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    api.bene.finance
    Type
    A
    Value
    103.160.59.100
  • Name
    bene.finance
    Type
    A
    Value
    103.160.59.100

DNSSEC valid

No

IP address

127.0.1.10

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

Registration record

Registrar
NICENIC INTERNATIONAL GROUP CO., LIMITED
Registered
Updated
Expires
Nameservers
  • ns3.my-ndns.com
  • ns4.my-ndns.com
Original source fields · JSON
Uuid
5414c833-f551-4148-a045-404878d6eba5
Final url
https://bene.finance/
Status
200
History
[
    {
        "url": "https://bene.finance/",
        "status": 200
    }
]
DOM structure hash
bbafe2ccc151325cd1582c38200dc9a20506e956fdd4d5d1d21a1d184e77d813
Document hash
1b5c6925a6b1ff914242737a2350fce75eb7032477363f6b713c8b7fa8c5bd6e
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "api.bene.finance",
        "type": "A",
        "value": "103.160.59.100"
    },
    {
        "name": "bene.finance",
        "type": "A",
        "value": "103.160.59.100"
    }
]
Dnssec valid
false
Ip
127.0.1.10

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

Registration record
{
    "registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
    "created": "2026-10-28T10:18:01Z",
    "updated": "2026-10-28T10:18:01Z",
    "expires": "2027-10-28T10:18:01Z",
    "nameservers": [
        "ns3.my-ndns.com",
        "ns4.my-ndns.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report
Separate monitor score · 10 / 100 · 2026-10-31T19:00:01Z

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
10
analyzed_at
2026-10-31T19:00:01Z
source_timestamp
2026-10-31 20:00:01
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
bene.finance — BeneX cryptocurrency exchange with manual support
ai_description
PhishDestroy records the bene.finance landing page, where BeneX invites visitors to calculate an amount and submit an exchange request.
ai_summary
The captured bene.finance page presents BeneX as a cryptocurrency exchange with personal support, headed by "Обмен криптовалют с личным сопровождением." The main interaction is a currency exchange widget labeled "Обмен валют" that currently shows "Загружаем валюты..." and a "Курс по заявке" note, alongside a three-step flow: submit a request, contact the operator in Telegram, and complete the exchange after payment verification. The page also links to exchange guides such as "Как проходит обмен" and network-specific tutorials. The stored VirusTotal domain result reports 0 detections out of 92 engines.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 19:56:10
revision
406481e8cb38896d842634d1e0a2e0a6f071ae1659a62cb0dae768cb56898a30
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 24 fields

Mail configuration

SPF lookups
0

CAA records

Domain
bene.finance

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
2
Archived days
3
Snapshots per day
0
Average page size, bytes
1724

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://bene.finance/sitemap.xml

Sitemap

Present
Yes
URL count
14

Page title and metadata

Open Graph URL
https://bene.finance/
Page title
BeneX — обмен криптовалют с ручным сопровождением
Open Graph type
website
Indexing directives
index, follow
Open Graph title
BeneX — обмен криптовалют с ручным сопровождением
Open Graph site name
BeneX
Theme color
#0f0a1a
Description
Обмен криптовалют в BeneX: расчёт суммы, выбор сети и заявка с сопровождением оператора в Telegram.
Twitter card
summary
Canonical URL
https://bene.finance/
Open Graph description
Обмен криптовалют в BeneX: расчёт суммы, выбор сети и заявка с сопровождением оператора в Telegram.

Trackers

Requests
5

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
211
TLS
26
Waiting
43
Connection
6
Download
0
Response time, ms
286

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 80
  • 443

Carbon estimate

Bytes
10071
CO₂, grams
0.0004
Cleaner than, %
72

DNS servers

Nameservers
  • IP address
    154.85.54.43
    Host
    ns3.my-ndns.com
  • IP address
    43.162.114.218
    Host
    ns4.my-ndns.com
DNS zone
bene.finance

Location

IP address
103.160.59.100
ASN
63023
Organization
GTHost
City
Berlin
Country
DE

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
bene.finance

DNS records

A
  • 103.160.59.100
NS
  • ns4.my-ndns.com
  • ns3.my-ndns.com
SOA
Primary nameserver
bene.finance
Hostmaster
root.bene.finance
Serial
2026102800
Refresh, seconds
7200
Retry, seconds
1800
Expiry, seconds
1209600
Minimum TTL, seconds
7200

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

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

HTTP security policies

X-Frame-Options
DENY
Referrer-Policy
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; co
Strict-Transport-Security
max-age=31536000
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
103.160.59.100
IP version
4

Redirects

Redirect chain
  • https://bene.finance

Page links

Internal links
12

HTTP headers

Response headers
Server
nginx
Content-type
text/html
Strict-transport-security
max-age=31536000
Content-security-policy
default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.bene.finance; object-src 'none'; base-uri 'self'; frame-ancestors 'none'
X-frame-options
DENY
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "bene.finance"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-31T18:23:22Z",
    "first": "2021-11-27T01:33:55Z",
    "changes": 2,
    "days_archived": 3,
    "scans_per_day": 0,
    "avg_page_bytes": 1724
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://bene.finance/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 14
}
Page title and metadata
{
    "ogUrl": "https://bene.finance/",
    "title": "BeneX — обмен криптовалют с ручным сопровождением",
    "ogType": "website",
    "robots": "index, follow",
    "ogTitle": "BeneX — обмен криптовалют с ручным сопровождением",
    "ogSiteName": "BeneX",
    "themeColor": "#0f0a1a",
    "description": "Обмен криптовалют в BeneX: расчёт суммы, выбор сети и заявка с сопровождением оператора в Telegram.",
    "twitterCard": "summary",
    "canonicalUrl": "https://bene.finance/",
    "ogDescription": "Обмен криптовалют в BeneX: расчёт суммы, выбор сети и заявка с сопровождением оператора в Telegram."
}
Trackers
{
    "requests": 5
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 211,
        "tls": 26,
        "wait": 43,
        "connect": 6,
        "download": 0
    },
    "response_ms": 286
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 10071,
    "co2_grams": 0.0004,
    "cleaner_than": 72
}
Dns server
{
    "ns": [
        {
            "ip": "154.85.54.43",
            "host": "ns3.my-ndns.com"
        },
        {
            "ip": "43.162.114.218",
            "host": "ns4.my-ndns.com"
        }
    ],
    "zone": "bene.finance"
}
Location
{
    "ip": "103.160.59.100",
    "asn": "63023",
    "org": "GTHost",
    "city": "Berlin",
    "country": "DE"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "bene.finance"
}
DNS records
{
    "A": [
        "103.160.59.100"
    ],
    "NS": [
        "ns4.my-ndns.com",
        "ns3.my-ndns.com"
    ],
    "SOA": "{\"nsname\": \"bene.finance\", \"hostmaster\": \"root.bene.finance\", \"serial\": 2026102800, \"refresh\": 7200, \"retry\": 1800, \"expire\": 1209600, \"minttl\": 7200}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000",
    "message": "HSTS header does not include all subdomains."
}
HTTP security policies
{
    "xFrameOptions": "DENY",
    "referrerPolicy": "strict-origin-when-cross-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; co",
    "strictTransportPolicy": "max-age=31536000",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "103.160.59.100",
    "family": 4
}
Redirects
{
    "chain": [
        "https://bene.finance"
    ]
}
Page links
{
    "internal_count": 12
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html",
        "strict-transport-security": "max-age=31536000",
        "content-security-policy": "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.bene.finance; object-src 'none'; base-uri 'self'; frame-ancestors 'none'",
        "x-frame-options": "DENY",
        "x-content-type-options": "nosniff",
        "referrer-policy": "strict-origin-when-cross-origin"
    }
}
Network Security Intelligence Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

Questions about bene.finance

Is bene.finance legit?

PhishDestroy records the bene.finance landing page, where BeneX invites visitors to calculate an amount and submit an exchange request.

Is bene.finance safe to connect a wallet?

This report does not record which wallet requests bene.finance 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 bene.finance?

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

Last checked

Stored Capture · 5 captures

All capture links and hashes (5)
Observed page title
BeneX — обмен криптовалют с ручным сопровождением
Automated brand references
Telegram
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 86 days

Domain details

Domain
IP Reputation Germany103.160.59.100 abuse score 0/100 0 reports checked Oct 31, 2026
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
RegistrationCreated Oct 28, 2026 (3d · Brand New!) — Expires Oct 28, 2027
Registrant countryAustralia VirusTotal WHOIS
Registrant1f8f4166599d23eec2d1ac5fad1b5b35s@contact.gandi.net VirusTotal WHOIS
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 10/1001 brand signal
Submitted URLhttps://bene.finance/
Favicon Hash
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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany103.160.59.100
Network ASN
AS63023
Organization
GTHost
Observed location
GermanyBerlin, DE
Server header
nginx

Nameservers 2

  • ns3.my-ndns.com
  • ns4.my-ndns.com

SOA

  • nsname: bene.finance
  • hostmaster: root.bene.finance
  • serial: 2026102800
  • refresh: 7200
  • retry: 1800
  • expire: 1209600
  • minttl: 7200

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-28 10:33:54
Valid until
2027-01-26 10:33:53
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint75fe294e282a1f59c920ca718622c97f4ecb4fef4a65f9c90f1a2c290fe24da8
Certificate names · 3 SANs
  • admin.bene.finance
  • api.bene.finance
  • bene.finance

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

Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of bene.finance · checked Oct 31, 2026

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

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

Archived HTTP response HTTP 200
Requested URL: https://bene.finance/
BeneX — обмен криптовалют с ручным сопровождением
Обмен криптовалют в BeneX: расчёт суммы, выбор сети и заявка с сопровождением оператора в Telegram.
Response
HTTP 200
HTML body
9.8 KB
Compressed
3.1 KB
Links
14 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Cache-Control: no-cache
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityContent-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsReferrer-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 1e7f6a9a02d40cbce3d00e718a487e9b204e33acd976542efc6500bd1dad0737
Open Graph title: BeneX — обмен криптовалют с ручным сопровождением
Open Graph description: Обмен криптовалют в BeneX: расчёт суммы, выбор сети и заявка с сопровождением оператора в Telegram.
Twitter card: summary
Saved response-header values · 14
Cache-Control
no-cache
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.bene.finance; object-src 'none'; base-uri 'self'; frame-ancestors 'none'
Content-Type
text/html
Date
Sat, 31 Oct 2026 18:23:20 GMT
Etag
W/"6ae3abb4-2757"
Last-Modified
Thu, 29 Oct 2026 20:25:24 GMT
Referrer-Policy
strict-origin-when-cross-origin
Server
nginx
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-Frame-Options
DENY

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

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: 9 SHA-256 hashes: 8 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-10-31 18:22 UTC.

Open this scan on URLScan 01a19331-ced6-73ea-978e-b758f214af1c ↗

Stored observation history1

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

  1. 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-10-31 19:22:38.000000
    Evidence SHA-256
    9063f489c24f4ad0e3ebff074192f9b14588317a2f4159020b9c7ab26550a680
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 19:22:38
    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-10-31 19:22:38.000000
    Evidence SHA-256
    9063f489c24f4ad0e3ebff074192f9b14588317a2f4159020b9c7ab26550a680
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 19:22:38
    Evidence reason

Threat Response Pipeline

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

Recorded events: 11. 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
    bene.finance detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · OTX Community References · Registrar Context: NiceNIC · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • Spamhaus DBL
    Spamhaus DBL recorded: spam domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 85
  • 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
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • Registrar Context: NiceNIC
    Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
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. AlienVault OTX

    3 community references

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    bene.finance

    View source
  4. URLScan

    Page captured

    View source
  5. VirusTotal

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

Check for cloaking

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

bene.finance

Evidence & External Reports

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.

Official reporting routes

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.

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 bene.finance)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/bene.finance"
  title="PhishDestroy threat report for bene.finance"
  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>