Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 13. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
pks-legal.com favicon

pks-legal.com

In short

pks-legal.com is a phishing page detected by PhishDestroy on 2026-10-19.

“Shared document”

Registrar
ODTU Gelistirme Vakfi …
Resolved IP
172.67.201.138
Registered
Mar 8, 2024
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 13/92
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
Not recorded
Page captures
open gallery
Domain age
Reports sent
view timeline
OTX: 4 refs Oct 19, 2026 1 Report Sent CDN
X Telegram API
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@metunic.com.tr. The latest stored availability evidence still shows the domain reachable; 7 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
7 days
Reports sent
1
Latest case ID
PD-20261019-E9A7D4
Current status
HTTP 301 at latest stored check

Analysis

Domain summary

pks-legal.com is a phishing page detected by PhishDestroy on 2026-10-19. Risk: critical (99/100). Registrar: ODTU Gelistirme Vakfi …. Status: Last known active. Hosting: CLOUDFLARENET - Cloudflare, Inc., US. PhishDestroy sent 1 abuse report. VirusTotal: 13/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
13 / 92
OTX
4 community refs
Page captures
3

PhishDestroy threat report

Overview

pks-legal.com is a domain on the PhishDestroy blocklist that mimics a legal or professional service to deceive visitors. PhishDestroy first observed the site on 2026-10-19. As of 2026-10-19, the site is marked as alive but its content is unreachable, indicating possible takedown or evasion attempts.

How the scam works

The site uses a legal or professional guise to lure users into interacting with it, potentially harvesting sensitive information or tricking users into actions that compromise their security. The page title and content were not accessible at the time of analysis, so the exact mechanism cannot be confirmed. However, the combination of blocklist flags and detections suggests a high risk of malicious behavior.

Evidence

VirusTotal flagged the domain with 5 detections out of 92 engines on 2026-10-19, including reports from alphaMountain.ai, CRDF, DNS8, Gridinsoft, and SOCRadar. The domain is also listed on PhishDestroy and OpenPhish blocklists and has 4 OTX pulses.

Infrastructure

The domain was registered on 2024-03-08 with ODTU Gelistirme Vakfi Bilgi Teknolojileri Sanayi Ve Ticaret Anonim Sirketi. It is hosted on a server with IP 172.67.201.138.

What to do

If you visited the site, disconnect from the internet and scan your device for malware. Do not enter any personal or financial information. Review recent transactions and revoke any suspicious app permissions or wallet connections. Defenders should block the domain and IP at the network level and monitor for related indicators.

Source evidenceVirusTotal 13 / 92 · OTX 4 references 10 sources

VirusTotal

13 / 92 engine detections

Open report

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report
Separate monitor record · 2026-10-20 03:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a151c9-0254-7256-bb34-337faeed0f86
score
0
malicious
false
result_at
2026-10-20T03:30:14Z
enriched_at
2026-10-19T08:10:36Z
source_timestamps
{"urlscan_result_at":"2026-10-20 05:30:14","urlscan_enriched_at":"2026-10-19 10:10:36"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 5 / 100 · 2026-10-19T02:20:14Z

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
5
analyzed_at
2026-10-19T02:20:14Z
source_timestamp
2026-10-19 04:20:14
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
pks-legal.com — Suspicious Domain
ai_description
pks-legal.com is a recently flagged domain on PhishDestroy and OpenPhish blocklists; it targets users with deceptive legal-themed content and shows signs of malicious.
ai_generated_at
2026-10-19T02:06:28Z
ai_generated_by
threat-mistral
interpretation
Narrative generation metadata, separate from provider observation dates.

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

Security Signals
SA Scamadviser Warnings 51/100
The owner of the website is using a service to hide their identity on WHOIS According to Tranco this site has a low rank This website has been reported for Phishing by IPQS This website has been reported as Suspicious by IPQS
The SSL certificate is valid This website is (very) old This website is safe according to DNSFilter

Questions about pks-legal.com

Is pks-legal.com legit?

No. PhishDestroy classifies pks-legal.com as a phishing page (risk: critical, 99/100); it was first detected on 2026-10-19. VirusTotal: 13/92 engines flag it. Treat the site as unsafe.

Is pks-legal.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on pks-legal.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used pks-legal.com?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 3 captures

All capture links and hashes (3)

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar ODTU Gelistirme Vakfi …
RegistrationCreated Mar 8, 2024 — Expires Mar 8, 2027
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedOct 19, 2026
DOM Analysisanalyzed Oct 19, 2026score 98/100
Submitted URLhttp://pks-legal.com/home
Favicon Hash
Case ID
Observed page title
Shared document
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 55 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.201.138
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • chin.ns.cloudflare.com
  • gerald.ns.cloudflare.com

Mail routing 1 MX record

  • pkslegal-com0i.mail.protection.outlook.compriority 10

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-21 18:07:44
Valid until
2026-12-20 19:07:33
Validity
Within stored validity dates
Collection time
2026-10-19 04:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint149b5ec145df3b7abeb54424d7c9700893c8b4851de7a64e6de6b3cd18bd52cf

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-10-25 23:42:45 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 Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-25 23:42:45 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-25 03:31:22 UTC last content: 2026-10-21 22:33:14 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.
Threat Intel Cross-Reference · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Fetched directly from the site by PhishDestroy · cached up to 24 h
Recorded subdomains2

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

  • vpn.pks-legal.comDomain record
  • www.pks-legal.comDomain record

The original observation time is not recorded for these hostnames.

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

13 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
BitDefender
CRDF
DNS8
Forcepoint ThreatSeeker
G-Data
Gridinsoft
Lionic
MalwareURL
Seclookup
SOCRadar
URLQuery
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of pks-legal.com · checked Oct 19, 2026

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

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

Archived HTTP response HTTP 200
Requested URL: http://pks-legal.com/home
Final URL: http://pks-legal.com/home/
Shared document
Response
HTTP 200
HTML body
14.6 KB
Compressed
5.0 KB
Links
1 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
Cache-Control: no-store
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
X-Content-Type-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 17
alt-svc
h3=":443"; ma=86400
Cache-Control
no-store
cf-cache-status
DYNAMIC
CF-RAY
a4cc095d78a5964a-YYZ
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Mon, 19 Oct 2026 01:33:46 GMT
Expires
Thu, 19 Nov 1981 08:52:00 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Pragma
no-cache
Referrer-Policy
no-referrer
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=x4%2FvbDK2%2B7jm69dx83CWtCvwUMYb7JD%2FJw2FRYmiKjfNytVLJ7E4MSfFMkrHwskDZtiby%2B94Vk3eMNK3ZG8ZZxitSBgs8LAtlGAEr7rURLRvRTFVEHA4qTzftQpyEGPw"}]}
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff

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

Registration & observation details3

Availability observations

Last reachable observation
Last content 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.

Stored observation history9

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

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    live_content→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 4
  1. Availability monitor · Recorded state

    redirected→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Domain monitor · First collection record

    Reachable

All retained availability observations34

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_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:42:45.000000
    Evidence SHA-256
    3c91c23d1d6a1adcf836e5ebc0f512c9d901b241eaf873fa3a561fa8f3f60cf8
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-26 00:42:45
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:42:45.000000
    Evidence SHA-256
    3c91c23d1d6a1adcf836e5ebc0f512c9d901b241eaf873fa3a561fa8f3f60cf8
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-26 00:42:45
    Evidence reason
    redirect
  3. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:40:48.000000
    Evidence SHA-256
    2bae182edb7d5a2630053dc09b4bbe0877473cfc928c49d4491c59cad31b6d6e
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-25 12:40:48
    Evidence reason
    redirect
  4. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:40:48.000000
    Evidence SHA-256
    2bae182edb7d5a2630053dc09b4bbe0877473cfc928c49d4491c59cad31b6d6e
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-25 12:40:48
    Evidence reason
    redirect
  5. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-25 09:55:07.418941
    Evidence SHA-256
    f29421045a2f0d44850c6f52d6d8bbdf0829af36630a6ed5c83feca2dfe013b6
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 09:55:07.418941
    Evidence reason
  6. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:31:22.000000
    Evidence SHA-256
    89445141aa5f607b7f068a8031e9d2b58da7f0014748d16f475d165c329d7ffc
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-25 04:31:22
    Evidence reason
    redirect
  7. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:31:22.000000
    Evidence SHA-256
    89445141aa5f607b7f068a8031e9d2b58da7f0014748d16f475d165c329d7ffc
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-25 04:31:22
    Evidence reason
    redirect
  8. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:35:21.000000
    Evidence SHA-256
    ee139dfc3ad04341d62dfb7ca44ba707210f4959fc1c595bf7893dc5732cd98f
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 12:35:21
    Evidence reason
    redirect
  9. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:35:21.000000
    Evidence SHA-256
    ee139dfc3ad04341d62dfb7ca44ba707210f4959fc1c595bf7893dc5732cd98f
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 12:35:21
    Evidence reason
    redirect
  10. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:37:53.000000
    Evidence SHA-256
    95d129258f2227c14e5cab197eea2cfb586f504c55bf4dde5c1929dee535ab2f
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 00:37:53
    Evidence reason
    redirect
  11. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:37:53.000000
    Evidence SHA-256
    95d129258f2227c14e5cab197eea2cfb586f504c55bf4dde5c1929dee535ab2f
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 00:37:53
    Evidence reason
    redirect
  12. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-23 22:56:16.207510
    Evidence SHA-256
    c5f098587335747ecb0284c1aaf394d9a7f57967b624ae64d7c6e3e96d6d5417
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 22:56:16.207510
    Evidence reason
  13. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:39:54.000000
    Evidence SHA-256
    4352dd8af0ceb5ff8cf11709814f83bb9e77daef98d556efc11256d3ead14b38
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-23 12:39:54
    Evidence reason
    redirect
  14. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:39:54.000000
    Evidence SHA-256
    4352dd8af0ceb5ff8cf11709814f83bb9e77daef98d556efc11256d3ead14b38
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-23 12:39:54
    Evidence reason
    redirect
  15. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 04:33:40.000000
    Evidence SHA-256
    5852357dc73ec1ed1e1a9e6938c3c140192638be268bc61d283d2473e419ef9f
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-23 04:33:40
    Evidence reason
    redirect
  16. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 04:33:40.000000
    Evidence SHA-256
    5852357dc73ec1ed1e1a9e6938c3c140192638be268bc61d283d2473e419ef9f
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-23 04:33:40
    Evidence reason
    redirect
  17. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-22 22:55:15.888363
    Evidence SHA-256
    3b646e5bc1bac379c47f59c89fb9159326ef6c40d3366eb6dfd5fa43e677c4aa
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-22 22:55:15.888363
    Evidence reason
  18. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 12:30:43.000000
    Evidence SHA-256
    de96aebd634fe830453a872473b8de86313449383908a6fffbce82ffbdbf487d
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-22 12:30:43
    Evidence reason
    redirect
  19. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 12:30:43.000000
    Evidence SHA-256
    de96aebd634fe830453a872473b8de86313449383908a6fffbce82ffbdbf487d
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-22 12:30:43
    Evidence reason
    redirect
  20. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 00:33:14.000000
    Evidence SHA-256
    781e52fa4916bb4289d192e49994d950e2daefe08ff5f9af041bccc958ff4d38
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-22 00:33:14
    Evidence reason
    alive_content
  21. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 00:33:14.000000
    Evidence SHA-256
    781e52fa4916bb4289d192e49994d950e2daefe08ff5f9af041bccc958ff4d38
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-22 00:33:14
    Evidence reason
    alive_content
  22. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-21 16:53:36.928467
    Evidence SHA-256
    80d44683077929d57cc69d3d485aa4d0ee469673c8067e794714c21730456f32
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-21 16:53:36.928467
    Evidence reason
  23. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 12:31:42.000000
    Evidence SHA-256
    b654ca992614f74b3f676f5782e2bec3f1c6cd47fa58e5304a776e06beb4ca56
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-21 12:31:42
    Evidence reason
    alive_content
  24. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 12:31:42.000000
    Evidence SHA-256
    b654ca992614f74b3f676f5782e2bec3f1c6cd47fa58e5304a776e06beb4ca56
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-21 12:31:42
    Evidence reason
    alive_content
  25. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 03:57:57.000000
    Evidence SHA-256
    95bd219729bc128083ff73b51ea4716e1e18da8cfc1801c0a6e0b48ae5cb8727
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-21 03:57:57
    Evidence reason
    redirect
  26. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 03:57:57.000000
    Evidence SHA-256
    95bd219729bc128083ff73b51ea4716e1e18da8cfc1801c0a6e0b48ae5cb8727
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-21 03:57:57
    Evidence reason
    redirect
  27. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-20 10:21:37.183325
    Evidence SHA-256
    f6ebc34c637ae5924f85300e39eeddc978e4821086a9222c87005e67a3b0d797
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-20 10:21:37.183325
    Evidence reason
  28. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-20 00:10:35.000000
    Evidence SHA-256
    1816be8cd09332cdb4d450e7c77ff68fc931a17192a1a2dd436c1523766a48bb
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-20 00:10:35
    Evidence reason
    redirect
  29. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-20 00:10:35.000000
    Evidence SHA-256
    1816be8cd09332cdb4d450e7c77ff68fc931a17192a1a2dd436c1523766a48bb
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-20 00:10:35
    Evidence reason
    redirect
  30. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 12:11:19.000000
    Evidence SHA-256
    7fd3011a27d181acc72372cbe002f462d3f60312e477f26a512b2c59411ea205
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-19 12:11:19
    Evidence reason
    redirect
  31. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 12:11:19.000000
    Evidence SHA-256
    7fd3011a27d181acc72372cbe002f462d3f60312e477f26a512b2c59411ea205
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-19 12:11:19
    Evidence reason
    redirect
  32. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-19 03:33:31.000000
    Evidence SHA-256
    2dbe35f84e3a815ae82cc9e8cae7eb7e119c8388968ca30eb17419f5ebc6c17c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 03:33:31
    Evidence reason
  33. 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-10-19 03:33:31.000000
    Evidence SHA-256
    2dbe35f84e3a815ae82cc9e8cae7eb7e119c8388968ca30eb17419f5ebc6c17c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 03:33:31
    Evidence reason
  34. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-18 22:24:26.306926
    Evidence SHA-256
    55592dd2563652f936d8a613702add1a293ada5ee28222cb642578e47583e9ce
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-18 22:24:26.306926
    Evidence reason

Recorded activity

6 entries
  1. VirusTotal

    13/92 engine detections

    View source
  2. AlienVault OTX

    4 community references

    View source
  3. Abuse report sent

    PD-20261019-E9A7D4

    abuse@metunic.com.tr
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    pks-legal.com

    View source
  6. URLScan

    Page captured

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

Check for cloaking

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

pks-legal.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261019-E9A7D4 Recipient: abuse@metunic.com.tr
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

7 evidence signal groups linked 1 stored notification records Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 pks-legal.com)
  • 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/pks-legal.com"
  title="PhishDestroy threat report for pks-legal.com"
  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>