Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 19. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
p.wesrki2bil.info favicon

p.wesrki2bil.info

In short

PhishDestroy records that p.wesrki2bil.info displayed a Cloudflare error 520 page reporting an unknown web server error.

Review the evidence
Resolved IP
Canada172.67.177.42Cloudflare, Inc. · CDN
First observed
Nov 1, 2026
PhishDestroy assessment Critical
95/100
Evidence score
First observed Nov 1, 2026 14:39 UTC · PhishDestroy
Risk signals
VirusTotal detections: 19/92 Spamhaus DBL: phishing domain
VirusTotal
19 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 69
Page captures
5
open gallery
Nov 1, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records that p.wesrki2bil.info displayed a Cloudflare error 520 page reporting an unknown web server error.

Critical
VirusTotal
19 / 92
Hosting
Canada172.67.177.42Cloudflare, Inc. · CDN
Page captures
5
Page captures Source results

PhishDestroy analysis, reviewed version

The captured page for p.wesrki2bil.info is a Cloudflare error screen stating that the web server is returning an unknown error, identified as error code 520. It shows a status strip where the browser and Cloudflare are marked working while the host p.wesrki2bil.info is marked error, and it explains that an unknown connection issue between Cloudflare and the origin web server prevents the page from being displayed, with guidance for visitors to try again later.

The stored VirusTotal domain result reports 19 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".

Source evidenceVirusTotal 19 / 92 8 sources

VirusTotal

19 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
41
Malicious
14
Suspicious
5
Undetected
32

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Fortinet
phishing
PREBYTES
phishing
SOCRadar
phishing
Kaspersky
phishing
LevelBlue
suspicious
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
spam
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • dga

Categories

PREBYTES
phishing

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    104.21.80.99
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.177.42

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.wesrki2bil.info
  • wesrki2bil.info
Issuer
Let's Encrypt / YE2
Serial
6e29a2d84c54b163dacaf9ccb8b04b86d96
SHA-256
9c8401d6158486d429c87cc4ab81d0dd578083999bfab762ee68fed6cfb279fa
Subject
wesrki2bil.info
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 41,
    "malicious": 14,
    "suspicious": 5,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "phishing",
    "PREBYTES": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "suspicious",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "spam",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "PREBYTES": "phishing"
}
First seen
2026-10-06T23:54:27Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.80.99"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.177.42"
    }
]
Dns at
2026-10-27T12:14:41Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.wesrki2bil.info",
        "wesrki2bil.info"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "6e29a2d84c54b163dacaf9ccb8b04b86d96",
    "sha256": "9c8401d6158486d429c87cc4ab81d0dd578083999bfab762ee68fed6cfb279fa",
    "subject": "wesrki2bil.info",
    "valid_to": "2027-01-01T20:14:27Z",
    "valid_from": "2026-10-03T20:14:28Z"
}
Separate source record · 14 malicious + 5 suspicious / 92 · 2026-10-27 12:09:21 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-27T12:09:21Z
fetched_at
2026-11-01T14:49:41Z
stats
{"timeout":0,"harmless":41,"malicious":14,"suspicious":5,"undetected":32}

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 69

SHA-256 40dd7170380e24baae73af4a18806107465b89a1bf770ae1ff3316a115eafde8

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a13a13-7ad3-77c4-a61e-d443dfae9ab7

Final URL

https://p.wesrki2bil.info/

HTTP response

520

Redirect type

https-only

Redirects

  • To
    https://p.wesrki2bil.info/
    From
    http://p.wesrki2bil.info/
    Status
    307

IP address

172.67.177.42

Contacted IP addresses

  • 172.67.177.42

Autonomous systems (ASN)

  • 13335

Linked domains

  • www.cloudflare.com
  • developers.cloudflare.com

Document hash

40dd7170380e24baae73af4a18806107465b89a1bf770ae1ff3316a115eafde8

TLS session and certificate

Subject alternative names
  • *.wesrki2bil.info
  • wesrki2bil.info
Cipher
AES_128_GCM
Issuer
YE2
Subject
wesrki2bil.info
Protocol
QUIC
Valid until
Valid from

Domain age, days

1

Registered domain age, days

10

Certificate age, days

10

Certificate validity, days

89

Page requests

8

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=UTF-8
X-frame-options
SAMEORIGIN
Referrer-policy
same-origin
Original source fields · JSON
Uuid
01a13a13-7ad3-77c4-a61e-d443dfae9ab7
Final url
https://p.wesrki2bil.info/
Status
520
Redirected
https-only
Redirects
[
    {
        "to": "https://p.wesrki2bil.info/",
        "from": "http://p.wesrki2bil.info/",
        "status": 307
    }
]
Ip
172.67.177.42
Contacted IP addresses
[
    "172.67.177.42"
]
Asns
[
    "13335"
]
Linked domains
[
    "www.cloudflare.com",
    "developers.cloudflare.com"
]
Document hash
40dd7170380e24baae73af4a18806107465b89a1bf770ae1ff3316a115eafde8
Tls
{
    "san": [
        "*.wesrki2bil.info",
        "wesrki2bil.info"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "wesrki2bil.info",
    "protocol": "QUIC",
    "valid_to": "2027-01-01T20:14:27Z",
    "valid_from": "2026-10-03T20:14:28Z"
}
Domain age days
1
Apex age days
10
Tls age days
10
Tls valid days
89
Requests
8
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 69,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8",
    "x-frame-options": "SAMEORIGIN",
    "referrer-policy": "same-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
01a13a13-7ad3-77c4-a61e-d443dfae9ab7
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

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

60f0844c-282e-4ffd-b13e-a73abd0ddf12

Final URL

https://p.wesrki2bil.info/

HTTP response

520

Navigation history

  • URL
    https://p.wesrki2bil.info/
    Status
    520

DOM structure hash

44f83b86670a53701e60f71195a3f41260783e3e1297f0ec6a48f6f4d16a372e

Document hash

0333de70e657308298c3d1814e343e062a79a57c8f8057bff23b48588e7557e1

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    p.wesrki2bil.info
    Type
    A
    Value
    172.67.177.42
  • Name
    p.wesrki2bil.info
    Type
    A
    Value
    104.21.80.99

DNSSEC valid

No

IP address

127.0.1.15

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

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware
Original source fields · JSON
Uuid
60f0844c-282e-4ffd-b13e-a73abd0ddf12
Final url
https://p.wesrki2bil.info/
Status
520
History
[
    {
        "url": "https://p.wesrki2bil.info/",
        "status": 520
    }
]
DOM structure hash
44f83b86670a53701e60f71195a3f41260783e3e1297f0ec6a48f6f4d16a372e
Document hash
0333de70e657308298c3d1814e343e062a79a57c8f8057bff23b48588e7557e1
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "p.wesrki2bil.info",
        "type": "A",
        "value": "172.67.177.42"
    },
    {
        "name": "p.wesrki2bil.info",
        "type": "A",
        "value": "104.21.80.99"
    }
]
Dnssec valid
false
Ip
127.0.1.15

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

Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}

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-01T15:04:50Z

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-01T15:04:50Z
source_timestamp
2026-11-01 16:04:50
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
p.wesrki2bil.info Cloudflare Error 520 Page
ai_description
PhishDestroy records that p.wesrki2bil.info displayed a Cloudflare error 520 page reporting an unknown web server error.
ai_summary
The captured page for p.wesrki2bil.info is a Cloudflare error screen stating that the web server is returning an unknown error, identified as error code 520. It shows a status strip where the browser and Cloudflare are marked working while the host p.wesrki2bil.info is marked error, and it explains that an unknown connection issue between Cloudflare and the origin web server prevents the page from being displayed, with guidance for visitors to try again later. The stored VirusTotal domain result reports 19 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 15:53:59
revision
fc98d09695d608922cb10d4d4a3fcba86abd708e48beeb888e223247b3a60c83
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

CAA records

Domain
p.wesrki2bil.info

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

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

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.34.98
    Host
    celine.ns.cloudflare.com
  • IP address
    162.159.44.52
    Host
    houston.ns.cloudflare.com
DNS zone
wesrki2bil.info

Location

IP address
104.21.80.99
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
wesrki2bil.info

DNS records

A
  • 104.21.80.99
  • 172.67.177.42

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
same-origin
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
104.21.80.99
IP version
4

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=UTF-8
X-frame-options
SAMEORIGIN
Referrer-policy
same-origin
Original source fields · JSON
Caa records
{
    "domain": "p.wesrki2bil.info"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-11-01T14:46:17Z",
    "first": "2026-11-01T14:46:17Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 1341
}
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.34.98",
            "host": "celine.ns.cloudflare.com"
        },
        {
            "ip": "162.159.44.52",
            "host": "houston.ns.cloudflare.com"
        }
    ],
    "zone": "wesrki2bil.info"
}
Location
{
    "ip": "104.21.80.99",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "wesrki2bil.info"
}
DNS records
{
    "A": [
        "104.21.80.99",
        "172.67.177.42"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": "SAMEORIGIN",
    "referrerPolicy": "same-origin",
    "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": "104.21.80.99",
    "family": 4
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8",
        "x-frame-options": "SAMEORIGIN",
        "referrer-policy": "same-origin"
    }
}

Questions about p.wesrki2bil.info

Is p.wesrki2bil.info legit?

PhishDestroy records that p.wesrki2bil.info displayed a Cloudflare error 520 page reporting an unknown web server error.

Is p.wesrki2bil.info safe to connect a wallet?

This report does not record which wallet requests p.wesrki2bil.info 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 p.wesrki2bil.info?

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: ec87146cb684f7a3bdd01fb27e385e9c0edfc3fd8f32b799ec1e36aac0fd835d SHA-256 of the prepared copy given to the model: 937221d186d79215dba8ddb14b273dba762d5b45e882373c857831e1e5a2b074
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status520
Final URLhttps://p.wesrki2bil.info/
Position1 / 5
Open capture Source Report Wayback Download
All capture links and hashes (5)

Domain details

Domain
IP Context Canada172.67.177.42 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 0/100
Submitted URLhttp://p.wesrki2bil.info/
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 61 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • celine.ns.cloudflare.com
  • houston.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-03 20:14:28
Valid until
2027-01-01 20:14:27
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint9c8401d6158486d429c87cc4ab81d0dd578083999bfab762ee68fed6cfb279fa
Certificate names · 2 SANs
  • *.wesrki2bil.info
  • wesrki2bil.info

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

VirusTotal Analysis

19 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
PREBYTES
Seclookup
SOCRadar
Sophos
VIPRE
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 404
Requested URL: http://p.wesrki2bil.info/
404 Not Found
Response
HTTP 404
HTML body
241 B
Compressed
184 B
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
Referrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 12
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a53bb2ec9876d371-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sun, 01 Nov 2026 14:48:11 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Referrer-Policy
no-referrer
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=6TNiZSbDObE9JVGjqPrlEpFVYC%2Fm%2BEc034olSnhJBHKirAJIPAKI6X0bCVfO%2BTdGlVgM35eYkNvsMC6QZWFmYX2AZEIUATZESvcGoRjYGPjwMAUoRH91jhMk3DDmW9hykBrwcA%3D
Server
cloudflare
Transfer-Encoding
chunked

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

Archived

Captured network requests

Network requests: 8 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-11-01 14:53 UTC.

Open this scan on URLScan 01a13a13-7ad3-77c4-a61e-d443dfae9ab7 ↗

All retained availability observations1

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
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 15:54:22.657419
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

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
    p.wesrki2bil.info detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • 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: 69
  • 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: 19/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.
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

3 entries
  1. Added to PhishDestroy

    p.wesrki2bil.info

    View source
  2. VirusTotal

    19/92 engine detections

    View source
  3. URLScan

    Malicious · engine verdict · score 69

    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.

p.wesrki2bil.info

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 19 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 Unverified
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 p.wesrki2bil.info)
  • 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/p.wesrki2bil.info"
  title="PhishDestroy threat report for p.wesrki2bil.info"
  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>