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

perlak.info

In short

The captured page for perlak.info presents itself as "Radek Perlak The Painter" and shows a dark-themed announcement about an exhibition opening at the National Museum in Vaduz, Liechtenstein, on 21 February 2018. A painting image sits beside Polish-language text describing the artist's second-place finish in the Zwischen hier und dort contest in Berlin, along with a link to an external contest site and a note that the Liechtenstein exhibition ran until 10 June 2018.

“Radek Perlak The Painter”

Review the evidence
Registrar
GermanyKey-Systems
Resolved IP
Poland89.161.144.21home.pl network
Registered
Dec 9, 2014
First observed
Nov 2, 2026
PhishDestroy assessment Critical
93/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 11/92
VirusTotal
11 / 92
engine detections ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 96
Page captures
5
open gallery
Domain age
4,345 days
registered 2014-12-09 according to WHOIS · source data differ
OTX: 1 ref Nov 2, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded perlak.info on 2026-11-02. VirusTotal: 11/92 engines flag it. Risk: critical (93/100). Registrar: Key-Systems. Status: Last known active. Hosting: home.pl network. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
11 / 92
Hosting
Poland89.161.144.21home.pl network
Registrar
GermanyKey-Systems
Registered
Dec 9, 2014
OTX
1 community ref
Page captures
5
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-11-02T03:07:05Z
SHA-256: d04146a87dc0479489c2fc50945c55b9777c96fb52fbb8f582ef218e966147f2

PhishDestroy analysis, reviewed version

The captured page for perlak.info presents itself as "Radek Perlak The Painter" and shows a dark-themed announcement about an exhibition opening at the National Museum in Vaduz, Liechtenstein, on 21 February 2018. A painting image sits beside Polish-language text describing the artist's second-place finish in the Zwischen hier und dort contest in Berlin, along with a link to an external contest site and a note that the Liechtenstein exhibition ran until 10 June 2018.

The stored VirusTotal domain result reports 11 detections out of 92 engines. ESET reported "suspicious"; VIPRE reported "malware".

Source evidenceVirusTotal 11 / 92 · OTX 1 references 8 sources

VirusTotal

11 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 16 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
48
Malicious
10
Suspicious
1
Undetected
33

Vendor labels

ESET
suspicious
VIPRE
malware
G-Data
phishing
Lionic
phishing
Sophos
phishing
Webroot
malicious
Fortinet
phishing
Seclookup
malicious
Gridinsoft
phishing
BitDefender
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
business and economy

Popularity ranks

Alexa
362049

Registrar

Key-Systems GmbH

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    3600
    Type
    MX
    Value
    perlak.info
    Priority
    10
  • TTL, seconds
    3600
    Type
    NS
    Value
    dns.home.pl
  • TTL, seconds
    60
    Type
    TXT
    Value
    v=spf1 a mx ~all
  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    admin.home.pl
    Value
    dns.home.pl
  • TTL, seconds
    3600
    Type
    NS
    Value
    dns2.home.pl
  • TTL, seconds
    3600
    Type
    NS
    Value
    dns3.home.pl
  • TTL, seconds
    3600
    Type
    A
    Value
    89.161.144.21

DNS records observed

JARM fingerprint

2ad2ad16d2ad2ad00042d42d000000df133019600a83abfb096ff3e86cd79d

Certificate

Subject alternative names
  • perlak.info
  • www.perlak.info
Issuer
home.pl S.A. / home pl DV TLS G2 R35 CA
Serial
53bfcc74e60d554c2cd8d12ac4e55498
SHA-256
812945f79950d0ce16fcbf2bf214d073d721ff8c4055b831f25a3e35a6f700f6
Subject
perlak.info
Valid until
Valid from

Registration record

Registrar
Key-Systems GmbH
Registrar IANA ID
269
Registrar URL
http://home.pl
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • dns.home.pl
  • dns2.home.pl
  • dns3.home.pl
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 48,
    "malicious": 10,
    "suspicious": 1,
    "undetected": 33
}
Vendor labels
{
    "ESET": "suspicious",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "business and economy"
}
Popularity
{
    "Alexa": 362049
}
Registrar
Key-Systems GmbH
Created
2014-12-09T17:04:57Z
Expires
2026-12-09T17:04:57Z
Updated
2024-12-11T20:44:05Z
First seen
2023-12-12T07:55:16Z
DNS records
[
    {
        "ttl": 3600,
        "type": "MX",
        "value": "perlak.info",
        "priority": 10
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns.home.pl"
    },
    {
        "ttl": 60,
        "type": "TXT",
        "value": "v=spf1 a mx ~all"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "admin.home.pl",
        "value": "dns.home.pl"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns2.home.pl"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns3.home.pl"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "89.161.144.21"
    }
]
Dns at
2026-10-28T12:44:52Z
Jarm
2ad2ad16d2ad2ad00042d42d000000df133019600a83abfb096ff3e86cd79d
Certificate
{
    "san": [
        "perlak.info",
        "www.perlak.info"
    ],
    "issuer": "home.pl S.A. / home pl DV TLS G2 R35 CA",
    "serial": "53bfcc74e60d554c2cd8d12ac4e55498",
    "sha256": "812945f79950d0ce16fcbf2bf214d073d721ff8c4055b831f25a3e35a6f700f6",
    "subject": "perlak.info",
    "valid_to": "2026-12-20T20:20:54Z",
    "valid_from": "2025-12-20T20:20:55Z"
}
Registration record
{
    "registrar": "Key-Systems GmbH",
    "registrar_iana_id": "269",
    "registrar_url": "http://home.pl",
    "created": "2014-12-09T17:04:57Z",
    "updated": "2024-12-06T20:43:05Z",
    "expires": "2026-12-09T17:04:57Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "dns.home.pl",
        "dns2.home.pl",
        "dns3.home.pl"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2028-12-09T17:04:57Z",
        "last changed": "2025-12-20T20:01:06Z",
        "registration": "2014-12-09T17:04:57Z",
        "registrar expiration": "2028-12-09T17:04:57Z",
        "last update of RDAP database": "2026-10-28T12:44:41Z"
    }
}
Separate source record · 10 malicious + 1 suspicious / 92 · 2026-10-28 12:41:54 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-28T12:41:54Z
fetched_at
2026-11-02T03:06:58Z
stats
{"timeout":0,"harmless":48,"malicious":10,"suspicious":1,"undetected":33}

URLScan

Malicious · engine verdict · score 96

SHA-256 df5037ca7eac1726e207693b0ccbb1f2ebe1a206bdbcffcc7587235dbf391294

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a19a38-34fb-710c-8fd5-a94117009361

Final URL

https://perlak.info/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://perlak.info/
    From
    http://perlak.info/
    Status
    307

IP address

89.161.144.21

Reverse DNS (PTR)

cloudserver024405.home.pl

Contacted IP addresses

  • 89.161.144.21

Autonomous systems (ASN)

  • 12824

Server countries

  • PL

Linked domains

  • artandprisonberlin.jimdoweb.com

Document hash

df5037ca7eac1726e207693b0ccbb1f2ebe1a206bdbcffcc7587235dbf391294

Script hashes

  • aaab5f92523f3443e527431c80a1d3ddb1bc3f3f7e677445fd309eb58d4db87e
  • fbe11af6f29f55ae480e2058aad3ac400315d2792c3b14346f016b70cebf3bb3
  • 063840b4b3f5869e0f0d078bab8bd29cfb3a59ee85e8e3edbbec35a8fe846fd3

JavaScript globals

  • _wpemojiSettings
  • twemoji
  • wp

Browser storage keys

  • wpEmojiSettingsSupports

TLS session and certificate

Subject alternative names
  • perlak.info
  • www.perlak.info
Cipher
AES_256_GCM
Issuer
home pl DV TLS G2 R35 CA
Subject
perlak.info
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1356

Differs from the registration date in WHOIS (2014-12-09), which gives 4345 days on the scan date 2026-11-02. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1356

Differs from the registration date in WHOIS (2014-12-09), which gives 4345 days on the scan date 2026-11-02. The two sources disagree; both values are kept as recorded.

Certificate age, days

316

Certificate validity, days

364

Page requests

10

Provider verdicts

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

HTTP headers

Server
IdeaWebServer/6.4.2
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a19a38-34fb-710c-8fd5-a94117009361
Final url
https://perlak.info/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://perlak.info/",
        "from": "http://perlak.info/",
        "status": 307
    }
]
Ip
89.161.144.21
Ptr
cloudserver024405.home.pl
Contacted IP addresses
[
    "89.161.144.21"
]
Asns
[
    "12824"
]
Countries
[
    "PL"
]
Linked domains
[
    "artandprisonberlin.jimdoweb.com"
]
Document hash
df5037ca7eac1726e207693b0ccbb1f2ebe1a206bdbcffcc7587235dbf391294
Script hashes
[
    "aaab5f92523f3443e527431c80a1d3ddb1bc3f3f7e677445fd309eb58d4db87e",
    "fbe11af6f29f55ae480e2058aad3ac400315d2792c3b14346f016b70cebf3bb3",
    "063840b4b3f5869e0f0d078bab8bd29cfb3a59ee85e8e3edbbec35a8fe846fd3"
]
Globals
[
    "_wpemojiSettings",
    "twemoji",
    "wp"
]
Storage keys
[
    "wpEmojiSettingsSupports"
]
Tls
{
    "san": [
        "perlak.info",
        "www.perlak.info"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "home pl DV TLS G2 R35 CA",
    "subject": "perlak.info",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-20T20:20:54Z",
    "valid_from": "2025-12-20T20:20:55Z"
}
Domain age days
1356

Differs from the registration date in WHOIS (2014-12-09), which gives 4345 days on the scan date 2026-11-02. The two sources disagree; both values are kept as recorded.

Apex age days
1356

Differs from the registration date in WHOIS (2014-12-09), which gives 4345 days on the scan date 2026-11-02. The two sources disagree; both values are kept as recorded.

Tls age days
316
Tls valid days
364
Requests
10
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 96,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "IdeaWebServer/6.4.2",
    "content-type": "text/html; charset=UTF-8"
}

OTX

1 community reference

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

ad5602bd-1c37-4a73-9cca-e0fbdf243f25

Final URL

https://perlak.info/

HTTP response

200

Navigation history

  • URL
    https://perlak.info/
    Status
    200

DOM structure hash

d33596cbeb5993c74a4820eb7fe3ae415dbff88e537607c4df2db2d05f5b32cf

Document hash

df5037ca7eac1726e207693b0ccbb1f2ebe1a206bdbcffcc7587235dbf391294

Domain risk categories

  • Arts
  • Entertainment

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    perlak.info
    Type
    A
    Value
    89.161.144.21

DNSSEC valid

No

IP address

127.0.1.2

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

Original source fields · JSON
Uuid
ad5602bd-1c37-4a73-9cca-e0fbdf243f25
Final url
https://perlak.info/
Status
200
History
[
    {
        "url": "https://perlak.info/",
        "status": 200
    }
]
DOM structure hash
d33596cbeb5993c74a4820eb7fe3ae415dbff88e537607c4df2db2d05f5b32cf
Document hash
df5037ca7eac1726e207693b0ccbb1f2ebe1a206bdbcffcc7587235dbf391294
Domain risks
[
    "Arts",
    "Entertainment"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "perlak.info",
        "type": "A",
        "value": "89.161.144.21"
    }
]
Dnssec valid
false
Ip
127.0.1.2

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

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
perlak.info - Radek Perlak The Painter exhibition announcement page
ai_description
PhishDestroy records perlak.info, a painter's site announcing an exhibition in Liechtenstein with a linked contest page.
ai_summary
The captured page for perlak.info presents itself as "Radek Perlak The Painter" and shows a dark-themed announcement about an exhibition opening at the National Museum in Vaduz, Liechtenstein, on 21 February 2018. A painting image sits beside Polish-language text describing the artist's second-place finish in the Zwischen hier und dort contest in Berlin, along with a link to an external contest site and a note that the Liechtenstein exhibition ran until 10 June 2018. The stored VirusTotal domain result reports 11 detections out of 92 engines. ESET reported "suspicious"; VIPRE reported "malware".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-02 04:08:14
revision
ae1f542627514acbb5ac3ad87bc9bedf95cf992a6384e9ee9aa1994459672c60
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: 23 fields

Mail configuration

MX records
  • perlak.info
SPF record
v=spf1 a mx ~all
DKIM
  • dkim
DKIM key size, bits
2048
SPF lookups
2

CAA records

Domain
perlak.info

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
54
Archived days
55
Snapshots per day
0.02
Average page size, bytes
12512

Page title and metadata

Page title
Radek Perlak The Painter
Indexing directives
max-image-preview:large
Generator
WordPress 7.1.4
Canonical URL
https://perlak.info/

Trackers

Requests
9

Forms and mixed content

Passive insecure
  • http://perlak.info/wp-content/uploads/2026/06/716-R.-Perlak-Self-portrait-2015-oil-on-canvas-40-x-32-in-100-x-81-cm-828x1024.jpg
Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
22
TLS
26
Waiting
547
Connection
22
Download
24
Response time, ms
641

TLS connection

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

Ports

Open ports
  • 21
  • 25
  • 80
  • 110
  • 143
  • 443
  • 587
  • 993
  • 995
  • 3306

Carbon estimate

Bytes
74174
CO₂, grams
0.0027
Cleaner than, %
28

DNS servers

Nameservers
  • IP address
    217.160.81.248
    Host
    dns2.home.pl
  • IP address
    217.160.80.244
    Host
    dns.home.pl
  • IP address
    185.132.34.251
    Host
    dns3.home.pl
DNS zone
perlak.info

Location

IP address
89.161.144.21
ASN
12824
Organization
home.pl network
City
Szczecin
Country
PL

TLS certificate

Issuer
home.pl S.A. / home pl DV TLS G2 R35 CA
Subject
perlak.info

DNS records

A
  • 89.161.144.21
MX
  • Mail server
    perlak.info
    Priority
    10
NS
  • dns2.home.pl
  • dns.home.pl
  • dns3.home.pl
SOA
Primary nameserver
dns.home.pl
Hostmaster
admin.home.pl
Serial
1564130715
Refresh, seconds
14400
Retry, seconds
7200
Expiry, seconds
2419200
Minimum TTL, seconds
3600
TXT
  • v=spf1 a mx ~all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
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

IP lookup

IP address
89.161.144.21
IP version
4

Redirects

Redirect chain
  • https://perlak.info

Subdomains

Count
1
Subdomains
  • www.perlak.info

Page links

External link addresses
  • https://artandprisonberlin.jimdoweb.com/
External links
1
Internal links
25

HTTP headers

Response headers
Server
IdeaWebServer/6.4.2
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Mail configuration
{
    "mx": [
        "perlak.info"
    ],
    "spf": "v=spf1 a mx ~all",
    "dkim": [
        "dkim"
    ],
    "dkim_bits": 2048,
    "spf_lookups": 2
}
Caa records
{
    "domain": "perlak.info"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-11-02T03:07:26Z",
    "first": "2018-08-08T19:41:19Z",
    "changes": 54,
    "days_archived": 55,
    "scans_per_day": 0.02,
    "avg_page_bytes": 12512
}
Page title and metadata
{
    "title": "Radek Perlak The Painter",
    "robots": "max-image-preview:large",
    "generator": "WordPress 7.1.4",
    "canonicalUrl": "https://perlak.info/"
}
Trackers
{
    "requests": 9
}
Forms and mixed content
{
    "passive_insecure": [
        "http://perlak.info/wp-content/uploads/2026/06/716-R.-Perlak-Self-portrait-2015-oil-on-canvas-40-x-32-in-100-x-81-cm-828x1024.jpg"
    ],
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 22,
        "tls": 26,
        "wait": 547,
        "connect": 22,
        "download": 24
    },
    "response_ms": 641
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        25,
        80,
        110,
        143,
        443,
        587,
        993,
        995,
        3306
    ]
}
Carbon
{
    "bytes": 74174,
    "co2_grams": 0.0027,
    "cleaner_than": 28
}
Dns server
{
    "ns": [
        {
            "ip": "217.160.81.248",
            "host": "dns2.home.pl"
        },
        {
            "ip": "217.160.80.244",
            "host": "dns.home.pl"
        },
        {
            "ip": "185.132.34.251",
            "host": "dns3.home.pl"
        }
    ],
    "zone": "perlak.info"
}
Location
{
    "ip": "89.161.144.21",
    "asn": "12824",
    "org": "home.pl network",
    "city": "Szczecin",
    "country": "PL"
}
Ssl
{
    "issuer": "home.pl S.A. / home pl DV TLS G2 R35 CA",
    "subject": "perlak.info"
}
DNS records
{
    "A": [
        "89.161.144.21"
    ],
    "MX": [
        "{\"exchange\": \"perlak.info\", \"priority\": 10}"
    ],
    "NS": [
        "dns2.home.pl",
        "dns.home.pl",
        "dns3.home.pl"
    ],
    "SOA": "{\"nsname\": \"dns.home.pl\", \"hostmaster\": \"admin.home.pl\", \"serial\": 1564130715, \"refresh\": 14400, \"retry\": 7200, \"expire\": 2419200, \"minttl\": 3600}",
    "TXT": [
        "v=spf1 a mx ~all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "89.161.144.21",
    "family": 4
}
Redirects
{
    "chain": [
        "https://perlak.info"
    ]
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.perlak.info"
    ]
}
Page links
{
    "external": [
        "https://artandprisonberlin.jimdoweb.com/"
    ],
    "external_count": 1,
    "internal_count": 25
}
HTTP headers
{
    "headers": {
        "server": "IdeaWebServer/6.4.2",
        "content-type": "text/html; charset=UTF-8"
    }
}

Questions about perlak.info

Is perlak.info legit?

PhishDestroy rates perlak.info as critical risk (93/100) from the recorded evidence; it was first recorded on 2026-11-02. VirusTotal: 11/92 engines flag it. Treat the site as unsafe.

Is perlak.info safe to connect a wallet?

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

PhishStats

Records in the PhishStats feed · 1

First seen
2026-06-09 23:38:48 UTC
IP address
89.161.144.21
Country
PL
Network
AS12824
Times seen
1
Recorded URLs (1)
  • https://perlak.info/wp-content/uploads/2026/01/Excel/Excel/Excel/Excel/?email=a@b.com2026-06-09 23:38:48 UTC · 89.161.144.21 · PL · AS12824

Stored Capture · 5 captures

Cloudflare Radar 1 / 5 Used in the analysis Source file SHA-256: d04146a87dc0479489c2fc50945c55b9777c96fb52fbb8f582ef218e966147f2 SHA-256 of the prepared copy given to the model: e48ca9321f79bf4a64a90785eda179e2d2a408e5e7e7261b485c5b3a24e1f332
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://perlak.info/
Position1 / 5
Open capture Source Report Wayback Download
All capture links and hashes (5)

Domain details

Domain
Registrar Key-Systems DE(DE)
Abuse contactabuse@key-systems.net, abuse@home.pl
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for perlak.info →
Hosting abuse contact abuse@home.pl home.pl network · AS12824
RegistrationCreated Dec 9, 2014 — Expires Dec 9, 2028
Registrant countryPoland VirusTotal WHOIS
Registrant1f8f4166599d23ee4babf6fcc6f7794as@domain-contact.org VirusTotal WHOIS
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 2, 2026
DOM Analysisanalyzed Nov 2, 2026score 0/100
Submitted URLhttp://perlak.info/
Favicon Hash
Observed page title
Radek Perlak The Painter
TLS Certificate
Issued by home.pl S.A. / home pl DV TLS G2 R35 CA · stored validity ends in 48 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Poland89.161.144.21
Network ASN
AS12824
Organization
home.pl network
Observed location
PolandSzczecin, PL
Server header
IdeaWebServer/6.4.2

Nameservers 3

  • dns.home.pl
  • dns2.home.pl
  • dns3.home.pl

SOA

  • nsname: dns.home.pl
  • hostmaster: admin.home.pl
  • serial: 1564130715
  • refresh: 14400
  • retry: 7200
  • expire: 2419200
  • minttl: 3600

Registrar abuse contact VirusTotal WHOIS

Mail routing 1 MX record

  • perlak.infopriority 10

Location describes the IP network.

TLS certificate

Issuer
home.pl S.A. / home pl DV TLS G2 R35 CA
Valid from
2025-12-20 20:20:55
Valid until
2026-12-20 20:20:54
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint812945f79950d0ce16fcbf2bf214d073d721ff8c4055b831f25a3e35a6f700f6
Certificate names · 2 SANs
  • perlak.info
  • www.perlak.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 · 89.161.144.21rapiddns.io
Recorded subdomains1

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

  • www.perlak.infoDomain record
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

11 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
ESET
Fortinet
G-Data
Gridinsoft
Lionic
Seclookup
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of perlak.info · checked Nov 2, 2026

97
Good
Performance
FCP
1.02 s
First Contentful Paint
LCP
2.38 s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
3.03 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://perlak.info/
Radek Perlak The Painter
Response
HTTP 200
HTML body
72.4 KB
Compressed
12.9 KB
Links
26 internal · 1 external
Detected technologies
jquerywordpress
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: IdeaWebServer/6.4.2
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 7
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Mon, 02 Nov 2026 03:07:08 GMT
Link
; rel="https://api.w.org/", ; rel="alternate"; title="JSON"; type="application/json", ; rel=shortlink
Server
IdeaWebServer/6.4.2
Transfer-Encoding
chunked

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

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

Captured network requests

Network requests: 10 SHA-256 hashes: 9 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-02 03:07 UTC.

Open this scan on URLScan 01a19a38-34fb-710c-8fd5-a94117009361 ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 04:06:37.000000
    Evidence SHA-256
    343e4162082a1f2504fc9f52ce11d64437eecd262434f0d4b733dd2ba0fe31ae
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 04:06:37
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 04:06:37.000000
    Evidence SHA-256
    343e4162082a1f2504fc9f52ce11d64437eecd262434f0d4b733dd2ba0fe31ae
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 04:06:37
    Evidence reason

Threat Response Pipeline

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

Recorded events: 10. 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
    perlak.info detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 96
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 11/92
  • OTX Community References
    Community publication references on AlienVault OTX: 1. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. Wayback Machine

    Page archived

    View source
  2. AlienVault OTX

    1 community references

    View source
  3. Added to PhishDestroy

    perlak.info

    View source
  4. URLScan

    Page captured

    View source
  5. VirusTotal

    11/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

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

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

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

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

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

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

perlak.info

Evidence & External Reports

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

Were You Affected by This Site?

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

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

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 perlak.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/perlak.info"
  title="PhishDestroy threat report for perlak.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>