Skip to security report
Dangerous

Phishing copy of Facebook

wk.pl favicon
Domain security and threat intelligence

wk.pl

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

On 2026-05-05, wk.pl displayed a page styled after Facebook's login interface. A blue header carries the Facebook wordmark alongside a Sign Up button and a compact email or phone and password form with a Log In button. The main panel shows a notice reading "You must log in to continue." above a "Log into Facebook" heading, with email or phone and password fields, a Log In button, a Forgot account? link, and a green Create new account button. A footer lists language options and links such as Sign Up, Log In, Messenger, and Privacy Policy, ending with Meta © 2026.

Page title: “Facebook”

More about the sources
Recorded security signals

Stored VirusTotal result: 13/92 engines flagged. Analysis time (as stored): 2026-11-09 18:21 UTC. Retrieved (as stored): 2026-11-10 21:31 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 13/92
Registrar
United KingdomNom-IQ
Resolved IP
Germany57.144.244.141Facebook, Inc
Registered
1999-03-30
First seen by PhishDestroy
2026-11-10
OTX
community references
Page captures
open gallery
Domain age
registered 1999-03-30 according to WHOIS · source data differ
OTX: 3 refs 2026-11-10

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded wk.pl on 2026-11-10. Stored VirusTotal result: 13/92 engines flagged. Analysis time (as stored): 2026-11-09 18:21 UTC. Retrieved (as stored): 2026-11-10 21:31 UTC. Risk: critical (evidence score 100/100). Registrar: Nom-IQ. Status: Last known active. Hosting: Facebook, Inc. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
13 / 92
Hosting
Germany57.144.244.141Facebook, Inc
Registrar
United KingdomNom-IQ
Registered
1999-03-30
OTX
3 community refs
Page captures
5

URLScan capture · 2026-05-05 11:02 UTC · SHA-256 ae1ce26a…d1108f6

PhishDestroy analysis, reviewed version

On 2026-05-05, wk.pl displayed a page styled after Facebook's login interface. A blue header carries the Facebook wordmark alongside a Sign Up button and a compact email or phone and password form with a Log In button. The main panel shows a notice reading "You must log in to continue." above a "Log into Facebook" heading, with email or phone and password fields, a Log In button, a Forgot account? link, and a green Create new account button. A footer lists language options and links such as Sign Up, Log In, Messenger, and Privacy Policy, ending with Meta © 2026.

The stored VirusTotal domain result reports 13 detections out of 92 engines. Bkav reported "malicious"; VIPRE reported "phishing".

Source evidenceVirusTotal 13 / 92 · OTX 3 references 8 sources

VirusTotal

13 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 11 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
13
Denominator
92
Vendors
alphaMountain.ai, Bkav, Chong Lua Dao, CyRadar, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky, Lionic, Seclookup, SOCRadar, Sophos, VIPRE, Webroot
Observed at
2026-11-09 18:21:23
Checked at
2026-11-10 22:31:15
Fetched at
2026-11-10 21:31:15

Gridinsoft

1/100

OTX

3 community references

Open report

URLScan

Page capture

SHA-256 d12c847d…d220fcf

Open report
URLScanOriginal source recordObserved: 24 fields
Separate monitor record

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
019df7cd-4017-705f-8255-008c0452d088
Enriched at
2026-11-11T09:14:22Z
Source timestamps
Urlscan enriched at: 2026-11-11 10:14:22

PhishDestroy DOM

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

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 25 / 100 · 2026-11-10 21:47 UTC

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

Heuristic score
25
Analyzed at
2026-11-10T21:47:18Z
Source timestamp
2026-11-10 22:47:18
Technical metadata

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
wk.pl: Recorded Facebook-style login page captured on 2026-05-05
AI description
PhishDestroy records wk.pl displaying a Facebook-branded login page with email or phone and password fields, captured on 2026-05-05.
AI summary
On 2026-05-05, wk.pl displayed a page styled after Facebook's login interface. A blue header carries the Facebook wordmark alongside a Sign Up button and a compact email or phone and password form with a Log In button. The main panel shows a notice reading "You must log in to continue." above a "Log into Facebook" heading, with email or phone and password fields, a Log In button, a Forgot account? link, and a green Create new account button. A footer lists language options and links such as Sign Up, Log In, Messenger, and Privacy Policy, ending with Meta © 2026. The stored VirusTotal domain result reports 13 detections out of 92 engines. Bkav reported "malicious"; VIPRE reported "phishing".
AI generated by
threat-v6-mimo
AI generated at
2026-11-10T21:37:04Z
Revision
bc1e9003a6caeede909e8b3a774d9f4829a60b922c1ee7d7a5fa305762f4d9ae
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: 17 fields

Mail configuration

SPF record
v=spf1 a ~all
SPF lookups
1

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
113
Archived days
214
Snapshots per day
0.02
Average page size, bytes
9051

Trackers

Requests
11
Observed services
  • Name
    Facebook CDN
    Company
    Meta
    Country
    US
    Category
    Hosting
    Requests
    11

TLS connection

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

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    129.134.30.12
    Host
    a.ns.facebook.com
  • IP address
    185.89.218.12
    Host
    c.ns.facebook.com
  • IP address
    129.134.31.12
    Host
    b.ns.facebook.com
  • IP address
    185.89.219.12
    Host
    d.ns.facebook.com
DNS zone
wk.pl

Location

IP address
2a03:2880:f084:10d:face:b00c:0:2
ASN
32934
Organization
Facebook, Inc.
City
Frankfurt am Main
Country
DE

TLS certificate

Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Subject
*.wk.pl

DNS records

A
  • 157.240.0.13
NS
  • c.ns.facebook.com
  • d.ns.facebook.com
  • a.ns.facebook.com
  • b.ns.facebook.com
SOA
Primary nameserver
a.ns.facebook.com
Hostmaster
dns.facebook.com
Serial
4207849484
Refresh, seconds
14400
Retry, seconds
1800
Expiry, seconds
604800
Minimum TTL, seconds
3600
TXT
  • 9yf990jc63flq91w1jlfz6lh2s5zmt5v
  • v=spf1 a ~all
AAAA
  • 2a03:2880:f084:10d:face:b00c:0:2

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000; preload; includeSubDomains
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

HTTP security policies

X-Frame-Options
DENY
Referrer-Policy
No
X-XSS-Protection
0
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
default-src 'self' blob: https://*.wk.pl https://*.fbcdn.net;script-src 'self' 'nonce-mTcbEuJt' blob: https://*.wk.pl ht
Strict-Transport-Security
max-age=31536000; preload; includeSubDomains
Cross-Origin-Opener-Policy
same-origin-allow-popups
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2a03:2880:f084:10d:face:b00c:0:2
IP version
6

Popularity rank

Domain
wk.pl

Registration record

Registered
Updated
Expires
Nameservers
  • a.ns.facebook.com.

HTTP headers

Response headers
Content-Type
text/html; charset="utf-8"
Strict-Transport-Security
max-age=31536000; preload; includeSubDomains
Content-Security-Policy
default-src 'self' blob: https://*.wk.pl https://*.fbcdn.net;script-src 'self' 'nonce-dbwKbv2o' blob: https://*.wk.pl https://*.fbcdn.net;style-src 'self' 'unsafe-inline' data: blob: https://*.wk.pl https://*.fbcdn.net;connect-src 'self' data: blob: https://*.wk.pl https://*.fbcdn.net;font-src 'self
X-Frame-Options
DENY
X-Content-Type-Options
nosniff
Cross-Origin-Opener-Policy
same-origin-allow-popups
Original source fields · JSON
Mail configuration
Spf: v=spf1 a ~all; Spf lookups: 1
Protective DNS results
Resolvers: 12; Blocked by: CloudFlare Family; Blocked count: 1
Web archive observations
Last: 2026-08-07T21:33:39Z; First: 2000-03-01T13:20:49Z; Changes: 113; Days archived: 214; Scans per day: 0.02; Avg page bytes: 9051
Trackers
Requests: 11; Trackers: (Name: Facebook CDN; Company: Meta; Country: US; Category: Hosting; Requests: 11)
TLS connection
Alpn: h2; Cipher: TLS_CHACHA20_POLY1305_SHA256; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443
DNS server
NS: (IP: 129.134.30.12; Host: a.ns.facebook.com), (IP: 185.89.218.12; Host: c.ns.facebook.com), (IP: 129.134.31.12; Host: b.ns.facebook.com), (IP: 185.89.219.12; Host: d.ns.facebook.com); Zone: wk.pl
Location
IP: 2a03:2880:f084:10d:face:b00c:0:2; ASN: 32934; Org: Facebook, Inc.; City: Frankfurt am Main; Country: DE
SSL
Issuer: DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1; Subject: *.wk.pl
DNS records
A: 157.240.0.13; NS: c.ns.facebook.com, d.ns.facebook.com, a.ns.facebook.com, b.ns.facebook.com; Soa: Nsname: a.ns.facebook.com; Hostmaster: dns.facebook.com; Serial: 4207849484; Refresh: 14400; Retry: 1800; Expire: 604800; Minttl: 3600; Txt: 9yf990jc63flq91w1jlfz6lh2s5zmt5v, v=spf1 a ~all; Aaaa: 2a03:2880:f084:10d:face:b00c:0:2
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Header: max-age=31536000; preload; includeSubDomains; Message: Site is compatible with the HSTS preload list!; Compatible: ✓
HTTP security policies
Xframeoptions: DENY; Referrerpolicy: ✗; Xxssprotection: 0; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: default-src 'self' blob: https://*.wk.pl https://*.fbcdn.net;script-src 'self' 'nonce-mTcbEuJt' blob: https://*.wk.pl ht; Stricttransportpolicy: max-age=31536000; preload; includeSubDomains; Crossoriginopenerpolicy: same-origin-allow-popups; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 2a03:2880:f084:10d:face:b00c:0:2; Family: 6
Rank
Domain: wk.pl
Registration record
Created: 1999-03-30T11:00:00Z; Updated: 2026-02-27T23:10:27Z; Expires: 2027-03-29T12:00:00Z; Nameservers: a.ns.facebook.com.
HTTP headers
Headers: Content type: text/html; charset="utf-8"; Strict transport security: max-age=31536000; preload; includeSubDomains; Content security policy: default-src 'self' blob: https://*.wk.pl https://*.fbcdn.net;script-src 'self' 'nonce-dbwKbv2o' blob: https://*.wk.pl https://*.fbcdn.net;style-src 'self' 'unsafe-inline' data: blob: https://*.wk.pl https://*.fbcdn.net;connect-src 'self' data: blob: https://*.wk.pl https://*.fbcdn.net;font-src 'self; X frame options: DENY; X content type options: nosniff; Cross origin opener policy: same-origin-allow-popups
Security Signals
SA Scamadviser Warnings 1/100
The website has been reported to have malware (e.g. viruses) Searching on Social Media we found negative links
According to the SSL check the certificate is valid DNSFilter considers this website safe
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security threats Phishing Phishing

Questions about wk.pl

Is wk.pl legit?

PhishDestroy rates wk.pl as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-11-10. Stored VirusTotal result: 13/92 engines flagged. Analysis time (as stored): 2026-11-09 18:21 UTC. Retrieved (as stored): 2026-11-10 21:31 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is wk.pl safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on wk.pl. A confirmed blockchain transaction cannot be reversed.

What should I do if I used wk.pl?

  • 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
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • 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 1
PhishDestroy PhishDestroy list View source

Page captures (5)

All capture links and hashes (5)

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation Germany57.144.244.141 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has a low abuse score, but the domain itself is recognized as phishing. 8 reports Port ScanHackingBrute-Force checked 2026-11-11 last reported
Registrar Nom-IQ GB(GB)
Abuse contactadmin@comlaude.com
RegistrationCreated 1999-03-30 — Expires 2027-03-29
HTTP Status301 Moved Permanently
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-10
DOM Analysisanalyzed 2026-11-10score 25/1002 brand signals
Submitted URLhttp://wk.pl/
Favicon Hash
Observed page title
Facebook
Automated brand references
Facebook Instagram
TLS Certificate
Issued by DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany57.144.244.141
Network ASN
AS32934
AS name
FACEBOOK - Facebook, Inc., US
Organization
Facebook, Inc
Observed location
GermanyFrankfurt am Main, DE

Nameservers 4

  • a.ns.facebook.com
  • b.ns.facebook.com
  • c.ns.facebook.com
  • d.ns.facebook.com

SOA

  • nsname: a.ns.facebook.com
  • hostmaster: dns.facebook.com
  • serial: 4207849484
  • refresh: 14400
  • retry: 1800
  • expire: 604800
  • minttl: 3600

Location describes the IP network.

TLS certificate

Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid from
2026-08-19 00:00:00
Valid until
2026-11-17 23:59:59
Hostname match
Yes
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprint16830d0338de282a99f99c012f3d38b98b520aa9d2311ea83799e95a5a42ce73
Certificate names · 2 SANs
  • *.wk.pl
  • wk.pl

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

Latest Classified Outcome 2026-11-21 11:21 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting DNS: Resolved
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-21 11:21 UTC
RDAP registration
Observed timeline last reachable: 2026-11-21 11:21 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains13

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

  • autoblachen.wk.plDomain record
  • cd5.wk.plDomain record
  • developers.wk.plDomain record
  • dns.wk.plDomain record
  • limatur.wk.plDomain record
  • mazbud.wk.plDomain record
  • my-od.wk.plDomain record
  • ramex.wk.plDomain record
  • staladam.wk.plDomain record
  • wiemjak.wk.plDomain record
  • www.fler.wk.plDomain record
  • www.wk.plDomain record
  • zamvinex.wk.plDomain record
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine

VirusTotal Analysis

13 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
Bkav
VIPRE
Lionic
Sophos
CyRadar
Webroot
SOCRadar
Kaspersky
Seclookup
Gridinsoft
Chong Lua Dao
alphaMountain.ai
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 92

Google PageSpeed Insights — mobile performance audit of wk.pl ·

92
Good
Performance
FCP
2.41 s
First Contentful Paint
LCP
2.49 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
172 ms
Total Blocking Time
SI
2.43 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 400
Requested URL: http://wk.pl/
Final URL: https://wk.pl/
Error
Response
HTTP 400
HTML body
1.5 KB
Compressed
833 B
Links
3 internal · 0 external
Selected response headers
Content-Encoding: gzip
Cache-Control: private, no-cache, no-store, must-revalidate
Content-Type: text/html; charset="utf-8"
Security headers present
Strict-Transport-SecurityContent-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionCross-Origin-Opener-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 24
Alt-Svc
h3=":443"; ma=86400
Cache-Control
private, no-cache, no-store, must-revalidate
Connection
keep-alive
Content-Encoding
gzip
Content-Length
833
Content-Security-Policy
default-src 'self' blob: https://*.wk.pl https://*.fbcdn.net;script-src 'self' 'nonce-zUdsfXf5' blob: https://*.wk.pl https://*.fbcdn.net;style-src 'self' 'unsafe-inline' data: blob: https://*.wk.pl https://*.fbcdn.net;connect-src 'self' data: blob: https://*.wk.pl https://*.fbcdn.net;font-src 'self' data: blob: https:
Content-Type
text/html; charset="utf-8"
cross-origin-embedder-policy-report-only
require-corp;report-to="coep_report"
Cross-Origin-Opener-Policy
same-origin-allow-popups
Date
Tue, 10 Nov 2026 21:33:09 GMT
document-policy
include-js-call-stacks-in-crash-reports
Expires
Sat, 01 Jan 2000 00:00:00 GMT
Origin-Agent-Cluster
?1
Pragma
no-cache
Proxy-Status
http_request_error; e_proxy="AcSJQ4VFG296p0J2-kgrW_8Np2Uk29DWIdbjDKnG_EaNS3qjUR6NL49VPt6cI9liS1YtRdPt6unhVvz-NfWXOw"; e_fb_twtaskhandle="AcTp5Wh-C2gRyQNRIUT4Ncva5BoAvmxvqoO_9t7a5PXFvdaQSa9hCSWdeJGoa5afiHicpoG1SAl2jP9hirtdBUxTlxX0UqNdnhxbfqZ
Report-To
{"max_age":2592000,"endpoints":[{"url":"https:\/\/www.facebook.com\/browser_reporting\/coop\/?minimize=0"}],"group":"coop_report","include_subdomains":true}, {"max_age":86400,"endpoints":[{"url":"https:\/\/www.facebook.com\/browser_reportin
Reporting-Endpoints
coop_report="https://www.facebook.com/browser_reporting/coop/?minimize=0", coep_report="https://www.facebook.com/browser_reporting/coep/?minimize=0"
Strict-Transport-Security
max-age=31536000; preload; includeSubDomains
Vary
Sec-Fetch-Site, Sec-Fetch-Mode
X-Content-Type-Options
nosniff
X-FB-Connection-Quality
EXCELLENT; q=0.9, rtt=4, rtx=0, c=10, mss=1380, tbw=3690, tp=-1, tpl=-1, uplat=23, ullat=0
X-FB-Debug
SmpHwE5nth+tTUAXLJhdPRyFvs50utxeAl8AdWQ1TwLbBQp5ppukX5YOSCGoKWAhpWx+MzInhVPVwVdwYBxeOQ==
X-Frame-Options
DENY
X-XSS-Protection
0

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

Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

All stored data114
Open complete records

Captured network requests

Network requests: 30 SHA-256 hashes: 30 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-10 21:53 UTC.

Open this scan on URLScan 01a1c772-071d-73ee-a199-3fb1e2b5fc24 ↗

Stored observation history11

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

  1. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  2. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  3. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  4. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  5. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

Earlier observations 6
  1. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  2. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  3. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  4. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  5. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  6. Domain monitor · First collection record

    Reachable

All retained availability observations39
Open complete records

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
  • Threat Ingested
    wk.pl detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Automated brand label: Facebook · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

5 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+10086 d 7 h
  3. Added to PhishDestroy+27 h 4 min
  1. URLScan

    Page captured

    +13 min
  2. Wayback Machine

    Page archived

    +6 min
  3. AlienVault OTX

    3 community references

    +7 min
  4. Added to PhishDestroy

    wk.pl

    +27 h 4 min
  5. VirusTotal

    13/92 engine detections

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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

wk.pl

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

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. Secure your accounts and funds first, then report. 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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

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.

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
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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 wk.pl)
  • 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/wk.pl"
  title="PhishDestroy threat report for wk.pl"
  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>