Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 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
resolve.bet favicon

resolve.bet

In short

PhishDestroy describes resolve.bet, where a Cloudflare security verification page reports an incompatible browser extension or network configuration.

“Resolve — Prediction Markets”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Canada104.21.57.100Cloudflare, Inc. · CDN
Registered
Aug 27, 2026
First observed
Nov 1, 2026
PhishDestroy assessment High
56/100
Evidence score
Availability Server error The latest stored response was inconclusive Observed HTTP probe
Risk signals
VirusTotal detections: 2/92
VirusTotal
2 / 92
engine detections ·
OTX
3
community references
URLScan
Malicious
engine verdict · score 85
Page captures
5
open gallery
Domain age
65 days
registered 2026-08-27 according to WHOIS · source data differ
OTX: 3 refs Nov 1, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy describes resolve.bet, where a Cloudflare security verification page reports an incompatible browser extension or network configuration.

High
Status
Server error
VirusTotal
2 / 92
Hosting
Canada104.21.57.100Cloudflare, Inc. · CDN
Registrar
United StatesDynadot
Registered
Aug 27, 2026
OTX
3 community refs
Page captures
5
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured resolve.bet page is a Cloudflare security verification screen rather than the site's prediction-market interface. It states that the website uses a security service to protect against malicious bots and that the page is displayed while the site verifies the visitor is not a bot. The main interaction is a troubleshooting guide: an error headed "Incompatible browser extension or network configuration" instructs the visitor to temporarily disable browser extensions, then use a "refresh this page" link, and to check firewall settings blocking "challenges.cloudflare.com" or try a different network, with links to Cloudflare's troubleshooting documentation.

The stored VirusTotal domain result reports 2 detections out of 92 engines. SOCRadar reported "malicious"; Gridinsoft reported "phishing".

Source evidenceVirusTotal 2 / 92 · OTX 3 references 8 sources

VirusTotal

2 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
57
Malicious
2
Suspicious
0
Undetected
33

Vendor labels

SOCRadar
malicious
Gridinsoft
phishing

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    aida.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    alexis.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.162.239
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3031::6815:3964
  • TTL, seconds
    21600
    Type
    NS
    Value
    aida.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3035::ac43:a2ef
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.57.100

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • resolve.bet
  • *.resolve.bet
Issuer
Google Trust Services / WE1
Serial
da954832490591f70e01d07a38121dee
SHA-256
101cc3176dc077db8149f36accaa8edbc71b8c20974b4f2fe73548e8cecd0b62
Subject
resolve.bet
Valid until
Valid from

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
DYNADOT LLC
Registrar IANA ID
472
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 57,
    "malicious": 2,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "SOCRadar": "malicious",
    "Gridinsoft": "phishing"
}
Reputation
0
Created
2024-10-18T00:00:00Z
Updated
2024-10-18T00:00:00Z
First seen
2024-10-19T07:14:33Z
DNS records
[
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "aida.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "alexis.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.162.239"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::6815:3964"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "aida.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3035::ac43:a2ef"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.57.100"
    }
]
Dns at
2026-10-30T07:58:31Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "resolve.bet",
        "*.resolve.bet"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "da954832490591f70e01d07a38121dee",
    "sha256": "101cc3176dc077db8149f36accaa8edbc71b8c20974b4f2fe73548e8cecd0b62",
    "subject": "resolve.bet",
    "valid_to": "2027-01-24T03:30:09Z",
    "valid_from": "2026-10-26T02:30:11Z"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-08-27T17:40:32Z",
        "last changed": "2026-08-27T19:21:55Z",
        "registration": "2026-08-27T17:40:32Z",
        "registrar expiration": "2027-08-27T17:40:32Z",
        "last update of RDAP database": "2026-10-23T11:09:18Z"
    },
    "registrar": "DYNADOT LLC",
    "registrar_iana_id": "472"
}
Separate source record · 2 malicious + 0 suspicious / 92 · 2026-10-30 07:58:17 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-30T07:58:17Z
fetched_at
2026-11-01T02:16:36Z
stats
{"timeout":0,"harmless":57,"malicious":2,"suspicious":0,"undetected":33}

URLScan

Malicious · engine verdict · score 85

SHA-256 23cef172e79327baad7b1794553cc9244a50705b18480cfba63ec159fc16e6b3

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a194e6-c2ac-71b8-aa57-a3beaad43803

Final URL

https://resolve.bet/

HTTP response

403

Redirect type

https-only

Redirects

  • To
    https://resolve.bet/
    From
    http://resolve.bet/
    Status
    307
  • To
    https://resolve.bet/
    From
    https://resolve.bet/
    Status
    307

IP address

172.67.162.239

Contacted domains

  • challenges.cloudflare.com

Contacted IP addresses

  • 104.18.94.41
  • 104.18.95.41
  • 172.67.162.239

Autonomous systems (ASN)

  • 13335

Linked domains

  • www.cloudflare.com

Document hash

23cef172e79327baad7b1794553cc9244a50705b18480cfba63ec159fc16e6b3

Script hashes

  • 0096da89079b3beb9b6b6f4fd46ee81d84213bb7a6ee42dd6ccf83dfb6b1858f

JavaScript globals

  • _cf_chl_opt
  • JwCUQ7
  • fXaz8
  • armBH3
  • YDta0
  • yCpNJ2
  • YMwdw2
  • Kncsd9
  • vJjAu8
  • AhhG9
  • iqzpL9
  • ENLzH2
  • Vnlyd3
  • GsfY1
  • Ewgxh3
  • uOdMb2
  • qwQRi7
  • sSEGO7
  • eJeI1
  • qgcO0
  • xNxMK4
  • pRxjE3
  • wsqXE7
  • sSkll6
  • nYPYj0
  • ZahLT8
  • Tlvt6
  • KryNx3
  • ygHP1
  • BWRSl4
  • angular
  • hbRVt7
  • TRcGA3
  • DIkC7
  • turnstile
  • txLfi5
  • kMLRO6
  • pOFU5
  • fxUea2

TLS session and certificate

Subject alternative names
  • resolve.bet
  • *.resolve.bet
Cipher
AES_128_GCM
Issuer
WE1
Subject
resolve.bet
Protocol
QUIC
Valid until
Valid from

Domain age, days

742

Differs from the registration date in WHOIS (2026-08-27), which gives 65 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Registered domain age, days

742

Differs from the registration date in WHOIS (2026-08-27), which gives 65 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Certificate age, days

5

Certificate validity, days

90

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
cloudflare
Content-type
text/html; charset=UTF-8
Content-security-policy
default-src 'none'; script-src 'nonce-cJQrMMhj0vC1rzDMuxNvvj' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.clou
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
same-origin
Permissions-policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),s
Cross-origin-opener-policy
same-origin
Cross-origin-resource-policy
same-origin
Cross-origin-embedder-policy
require-corp
Original source fields · JSON
Uuid
01a194e6-c2ac-71b8-aa57-a3beaad43803
Final url
https://resolve.bet/
Status
403
Redirected
https-only
Redirects
[
    {
        "to": "https://resolve.bet/",
        "from": "http://resolve.bet/",
        "status": 307
    },
    {
        "to": "https://resolve.bet/",
        "from": "https://resolve.bet/",
        "status": 307
    }
]
Ip
172.67.162.239
Contacted domains
[
    "challenges.cloudflare.com"
]
Contacted IP addresses
[
    "104.18.94.41",
    "104.18.95.41",
    "172.67.162.239"
]
Asns
[
    "13335"
]
Linked domains
[
    "www.cloudflare.com"
]
Document hash
23cef172e79327baad7b1794553cc9244a50705b18480cfba63ec159fc16e6b3
Script hashes
[
    "0096da89079b3beb9b6b6f4fd46ee81d84213bb7a6ee42dd6ccf83dfb6b1858f"
]
Globals
[
    "_cf_chl_opt",
    "JwCUQ7",
    "fXaz8",
    "armBH3",
    "YDta0",
    "yCpNJ2",
    "YMwdw2",
    "Kncsd9",
    "vJjAu8",
    "AhhG9",
    "iqzpL9",
    "ENLzH2",
    "Vnlyd3",
    "GsfY1",
    "Ewgxh3",
    "uOdMb2",
    "qwQRi7",
    "sSEGO7",
    "eJeI1",
    "qgcO0",
    "xNxMK4",
    "pRxjE3",
    "wsqXE7",
    "sSkll6",
    "nYPYj0",
    "ZahLT8",
    "Tlvt6",
    "KryNx3",
    "ygHP1",
    "BWRSl4",
    "angular",
    "hbRVt7",
    "TRcGA3",
    "DIkC7",
    "turnstile",
    "txLfi5",
    "kMLRO6",
    "pOFU5",
    "fxUea2"
]
Tls
{
    "san": [
        "resolve.bet",
        "*.resolve.bet"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "resolve.bet",
    "protocol": "QUIC",
    "valid_to": "2027-01-24T03:30:09Z",
    "valid_from": "2026-10-26T02:30:11Z"
}
Domain age days
742

Differs from the registration date in WHOIS (2026-08-27), which gives 65 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Apex age days
742

Differs from the registration date in WHOIS (2026-08-27), which gives 65 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Tls age days
5
Tls valid days
90
Requests
9
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 85,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8",
    "content-security-policy": "default-src 'none'; script-src 'nonce-cJQrMMhj0vC1rzDMuxNvvj' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.clou",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "same-origin",
    "permissions-policy": "accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),s",
    "cross-origin-opener-policy": "same-origin",
    "cross-origin-resource-policy": "same-origin",
    "cross-origin-embedder-policy": "require-corp"
}
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
01a08e61-3fa8-758f-97b2-7c8bd3c42df8
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

3 community references

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

39b9b399-6fc6-4d82-ad2d-bc2c4bad0b26

Final URL

https://resolve.bet/

HTTP response

403

Navigation history

  • URL
    https://resolve.bet/
    Status
    403

DOM structure hash

09471bf8e29d5571159827bc83d881c38e2f56d8a5b71911b3689b846bb80841

Document hash

584b810a593474e53a84fc989a80686d2e57ae3d5c39ca08a96743bbdb0c5c86

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    resolve.bet
    Type
    A
    Value
    172.67.162.239
  • Name
    resolve.bet
    Type
    A
    Value
    104.21.57.100
  • Name
    resolve.bet
    Type
    AAAA
    Value
    2606:4700:3035::ac43:a2ef
  • Name
    resolve.bet
    Type
    AAAA
    Value
    2606:4700:3031::6815:3964

DNSSEC valid

No

IP address

127.0.1.7

127.0.1.7 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
  • alexis.ns.cloudflare.com
  • aida.ns.cloudflare.com
Original source fields · JSON
Uuid
39b9b399-6fc6-4d82-ad2d-bc2c4bad0b26
Final url
https://resolve.bet/
Status
403
History
[
    {
        "url": "https://resolve.bet/",
        "status": 403
    }
]
DOM structure hash
09471bf8e29d5571159827bc83d881c38e2f56d8a5b71911b3689b846bb80841
Document hash
584b810a593474e53a84fc989a80686d2e57ae3d5c39ca08a96743bbdb0c5c86
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "resolve.bet",
        "type": "A",
        "value": "172.67.162.239"
    },
    {
        "name": "resolve.bet",
        "type": "A",
        "value": "104.21.57.100"
    },
    {
        "name": "resolve.bet",
        "type": "AAAA",
        "value": "2606:4700:3035::ac43:a2ef"
    },
    {
        "name": "resolve.bet",
        "type": "AAAA",
        "value": "2606:4700:3031::6815:3964"
    }
]
Dnssec valid
false
Ip
127.0.1.7

127.0.1.7 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-08-27T17:40:32Z",
    "updated": "2026-09-01T17:40:45Z",
    "expires": "2027-08-27T17:40:32Z",
    "nameservers": [
        "alexis.ns.cloudflare.com",
        "aida.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

15 / 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
resolve.bet — Cloudflare security verification blocked
ai_description
PhishDestroy describes resolve.bet, where a Cloudflare security verification page reports an incompatible browser extension or network configuration.
ai_summary
The captured resolve.bet page is a Cloudflare security verification screen rather than the site's prediction-market interface. It states that the website uses a security service to protect against malicious bots and that the page is displayed while the site verifies the visitor is not a bot. The main interaction is a troubleshooting guide: an error headed "Incompatible browser extension or network configuration" instructs the visitor to temporarily disable browser extensions, then use a "refresh this page" link, and to check firewall settings blocking "challenges.cloudflare.com" or try a different network, with links to Cloudflare's troubleshooting documentation. The stored VirusTotal domain result reports 2 detections out of 92 engines. SOCRadar reported "malicious"; Gridinsoft reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 03:18:44
revision
619b7023d007c1373f89514c253cf50b52d6ea7367a379ab32e5abb0dffaacb5
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: 15 fields

Mail configuration

SPF lookups
0

CAA records

Domain
resolve.bet

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
383

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

DNS servers

Nameservers
  • IP address
    172.64.32.58
    Host
    aida.ns.cloudflare.com
  • IP address
    173.245.59.60
    Host
    alexis.ns.cloudflare.com
DNS zone
resolve.bet

Location

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

TLS certificate

Issuer
Google Trust Services / WE1
Subject
resolve.bet

DNS records

A
  • 104.21.57.100
  • 172.67.162.239
NS
  • alexis.ns.cloudflare.com
  • aida.ns.cloudflare.com
SOA
Primary nameserver
aida.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418471123
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3031::6815:3964
  • 2606:4700:3035::ac43:a2ef

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:3035::ac43:a2ef
IP version
6

Subdomains

Count
1
Subdomains
  • www.resolve.bet

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=UTF-8
Content-security-policy
default-src 'none'; script-src 'nonce-WRuJIcK3y70QzkGvCQcyRk' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenge
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
same-origin
Permissions-policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
Cross-origin-opener-policy
same-origin
Cross-origin-resource-policy
same-origin
Cross-origin-embedder-policy
require-corp
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "resolve.bet"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2025-07-10T00:13:08Z",
    "first": "2025-07-10T00:13:08Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 383
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.32.58",
            "host": "aida.ns.cloudflare.com"
        },
        {
            "ip": "173.245.59.60",
            "host": "alexis.ns.cloudflare.com"
        }
    ],
    "zone": "resolve.bet"
}
Location
{
    "ip": "2606:4700:3035::ac43:a2ef",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "resolve.bet"
}
DNS records
{
    "A": [
        "104.21.57.100",
        "172.67.162.239"
    ],
    "NS": [
        "alexis.ns.cloudflare.com",
        "aida.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"aida.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418471123, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:3031::6815:3964",
        "2606:4700:3035::ac43:a2ef"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:3035::ac43:a2ef",
    "family": 6
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.resolve.bet"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8",
        "content-security-policy": "default-src 'none'; script-src 'nonce-WRuJIcK3y70QzkGvCQcyRk' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenge",
        "x-frame-options": "SAMEORIGIN",
        "x-content-type-options": "nosniff",
        "referrer-policy": "same-origin",
        "permissions-policy": "accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*",
        "cross-origin-opener-policy": "same-origin",
        "cross-origin-resource-policy": "same-origin",
        "cross-origin-embedder-policy": "require-corp"
    }
}

Questions about resolve.bet

Is resolve.bet legit?

PhishDestroy describes resolve.bet, where a Cloudflare security verification page reports an incompatible browser extension or network configuration.

Is resolve.bet safe to connect a wallet?

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

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

Cloudflare Radar 1 / 5 Used in the analysis Source file SHA-256: d0a5406e12995acbd453ef4ccc4dfa643555d0b9d75dca48b9b15a2c65d1def3 SHA-256 of the prepared copy given to the model: 24a8126870848686f1c97b7ddb465325697b8f709b6eb058f921408d4cbb7343
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status403
Final URLhttps://resolve.bet/
Position1 / 5
Open capture Source Report Wayback Download
All capture links and hashes (5)
Observed page title
Resolve — Prediction Markets
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 83 days

Domain details

Domain
IP Context Canada104.21.57.100 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags affiliate fraudai-assisted scamsatlascorecryptocurrency fraudmagnetic teamphishingpolyfuckedprediction marketstraffertraffer teams
Registrar Dynadot US(US)
Abuse contactabuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for resolve.bet →
RegistrationCreated Aug 27, 2026 (65d · New) — Expires Aug 27, 2027
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 15/100
Submitted URLhttp://resolve.bet/
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.

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
Canada104.21.57.100
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • aida.ns.cloudflare.com
  • alexis.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-10-26 02:30:11
Valid until
2027-01-24 03:30:09
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint101cc3176dc077db8149f36accaa8edbc71b8c20974b4f2fe73548e8cecd0b62
Certificate names · 2 SANs
  • resolve.bet
  • *.resolve.bet

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

viewdns.info · 104.21.57.100rapiddns.io
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.resolve.betDomain record
Casino / Gambling License Verification
Unverified gambling license
This domain markets casino/gambling services. Scam casinos routinely display fake Curaçao, MGA, or Kahnawake license badges that don’t exist in the real registries. Always verify the license number against the official regulator database before depositing. If the site shows a seal but no clickable registry link — or the linked registry page doesn’t exist — treat it as fraudulent.
Curaçao eGaming (official) Malta Gaming Authority UK Gambling Commission PA Gaming Control Kahnawake Gaming Gibraltar Gambling
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed
Gridinsoft
SOCRadar
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of resolve.bet · checked Nov 1, 2026

100
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
0.76 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
70 ms
Total Blocking Time
SI
1.12 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 403
Requested URL: http://resolve.bet/
Just a moment...
Response
HTTP 403
HTML body
5.5 KB
Compressed
3.2 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
CF-Mitigated: challenge
Server: cloudflare
Content-Encoding: gzip
Security headers present
Content-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsReferrer-PolicyPermissions-PolicyCross-Origin-Opener-PolicyCross-Origin-Resource-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 23
Accept-Ch
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
alt-svc
h3=":443"; ma=86400
Cf-Mitigated
challenge
CF-RAY
a5376545fa08dbcb-FRA
Connection
close
Content-Encoding
gzip
Content-Security-Policy
default-src 'none'; script-src 'nonce-AS8DgikrhQ3MqPzNzxfDOW' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blo
Content-Type
text/html; charset=UTF-8
Critical-Ch
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
Cross-Origin-Embedder-Policy
require-corp
Cross-Origin-Opener-Policy
same-origin
Cross-Origin-Resource-Policy
same-origin
Date
Sun, 01 Nov 2026 02:16:07 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Origin-Agent-Cluster
?1
Permissions-Policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
Referrer-Policy
same-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=QsVWyZhldJwE4RDMPLUUBYiAXxay%2FoEPagGavbH1PCJWzgcNcN%2FGUJFkDbTqxlm9ZT5vlLyKNZP%2Bsnoy06HoxDr6QC9OPP4Bi%2B0CB61%2Fyxz8Bbj%2Frvkg3BZv3axhZQ%3D%3
Server
cloudflare
Server-Timing
chlray;desc="a5376545fa08dbcb"
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN

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: 9 SHA-256 hashes: 6 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-01 02:20 UTC.

Open this scan on URLScan 01a194e6-c2ac-71b8-aa57-a3beaad43803 ↗

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
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:20:10.000000
    Evidence SHA-256
    848938f3cf6feb38f093f477bfe9e650bff3b881bcd83a695aa5dd5d674fc48a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 03:20:10
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:20:10.000000
    Evidence SHA-256
    848938f3cf6feb38f093f477bfe9e650bff3b881bcd83a695aa5dd5d674fc48a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 03:20:10
    Evidence reason

Threat Response Pipeline

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

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
    resolve.bet detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • 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.
  • VirusTotal
    Detections recorded on VirusTotal: 2/92
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • 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 Recorded: 1 of 1

Recorded activity

4 entries
  1. URLScan

    Page captured

    View source
  2. AlienVault OTX

    3 community references

    View source
  3. Added to PhishDestroy

    resolve.bet

    View source
  4. VirusTotal

    2/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

Check for cloaking

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

resolve.bet

Evidence & External Reports

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

Were You Affected by This Site?

4 evidence signal groups linked Server error
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 resolve.bet)
  • 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/resolve.bet"
  title="PhishDestroy threat report for resolve.bet"
  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>