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

gdzieswkorytarzu.top

In short

gdzieswkorytarzu.top is a phishing page detected by PhishDestroy on 2026-10-27.

“Привет Лось!”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Germany195.181.166.158Datacamp Limited · CDN
Registered
Jun 4, 2026
First observed
Oct 27, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 18/92
VirusTotal
18 / 92
engine detections ·
OTX
3
community references
URLScan
Malicious
engine verdict · score 92
Page captures
4
open gallery
Domain age
145 days
OTX: 3 refs Oct 27, 2026 CDN
X Telegram API

Analysis

Domain summary

gdzieswkorytarzu.top is a phishing page detected by PhishDestroy on 2026-10-27. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: Datacamp Limited. VirusTotal: 18/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
18 / 92
Hosting
Germany195.181.166.158Datacamp Limited · CDN
Registrar
United StatesDynadot
Registered
Jun 4, 2026
OTX
3 community refs
Page captures
4
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy listed gdzieswkorytarzu.top on 2026-10-27 after a trusted intake rule flagged the domain because it was 145 days old. The page title recorded at that time was "Привет Лось!" and the HTTP response was 200. An earlier urlscan capture on 2026-06-10 showed a 404 response after a 307 redirect to HTTPS.

How the scam works

The available evidence does not reveal a concrete phishing, wallet‑draining, or malware delivery flow. Detections label the domain as a possible DGA‑generated or malware‑associated site, a pattern often used to host malicious content or to evade detection, but no malicious payload or credential‑harvesting form was observed on the captured page.

Evidence

VirusTotal (2026-10-20) reported 18 detections from 92 engines, including 14 malicious and 4 suspicious labels from vendors such as BitDefender, ESET and Forcepoint. Google Safe Browsing (2026-10-27) returned no warning. PhishDestroy’s internal blocklist lists the domain and OTX recorded three pulses referencing it (checked 2026-10-27). urlscan.io (2026-06-10) gave the URL a 92‑point malicious engine score while its overall verdict was non‑malicious, and Cloudflare Radar (2026-10-27) flagged it as malicious under "dga domains" and "malware" categories.

Infrastructure

The domain was registered with Dynadot LLC on 2026-06-04. The recorded DNS records listed Cloudflare nameservers adaline.ns.cloudflare.com and logan.ns.cloudflare.com and showed IP addresses such as 195.181.166.158 (Datacamp Limited, DE) and a Cloudflare CDN address 104.21.0.219. TLS is provided by a Let's Encrypt certificate valid from 2026-10-04 to 2027-01-02. No further infrastructure details indicate operator identity.

What to do

Visitors who have not entered credentials or wallet information face no immediate compromise, but should avoid interacting with the site and delete any saved data. If credentials were entered, change passwords and enable MFA where possible. Defenders should block the domain at the firewall or proxy, monitor DNS queries for the domain, and log any access attempts for further analysis.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-27T19:58:05Z)URLScan screenshot (2026-06-09T11:45:26Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 18 / 92 · OTX 3 references 8 sources

VirusTotal

18 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
42
Malicious
14
Suspicious
4
Undetected
32

Vendor labels

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

Reputation score

0

Tags

  • dga

Registrar

Dynadot LLC

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    35
    Type
    AAAA
    Value
    2400:52e0:1a00::1235:1
  • TTL, seconds
    35
    Type
    A
    Value
    143.244.60.193
  • TTL, seconds
    21600
    Type
    NS
    Value
    elisabeth.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    logan.ns.cloudflare.com
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    elisabeth.ns.cloudflare.com

DNS records observed

JARM fingerprint

28d28d28d00028d1ec42d42d000000d6af9a39127f727c515e10d2758dee00

Certificate

Subject alternative names
  • gdzieswkorytarzu.top
Issuer
Let's Encrypt / YE2
Serial
6414eebfabc4b2a3a74de10fd8d1cf0e7f8
SHA-256
1b96c806db210e7d3c70b9124a837d03c7ad6c4182f2a5805ac022976d59ff28
Subject
gdzieswkorytarzu.top
Valid until
Valid from

Registration record

Registrar
Dynadot LLC
Registrar IANA ID
472
Registrar URL
http://www.dynadot.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • adaline.ns.cloudflare.com
  • logan.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 42,
    "malicious": 14,
    "suspicious": 4,
    "undetected": 32
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "suspicious",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
Dynadot LLC
Created
2026-06-04T07:20:39Z
Expires
2027-06-04T07:20:39Z
Updated
2026-06-04T07:24:00Z
First seen
2026-06-04T07:56:21Z
DNS records
[
    {
        "ttl": 35,
        "type": "AAAA",
        "value": "2400:52e0:1a00::1235:1"
    },
    {
        "ttl": 35,
        "type": "A",
        "value": "143.244.60.193"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "elisabeth.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "logan.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "elisabeth.ns.cloudflare.com"
    }
]
Dns at
2026-10-20T07:57:10Z
Jarm
28d28d28d00028d1ec42d42d000000d6af9a39127f727c515e10d2758dee00
Certificate
{
    "san": [
        "gdzieswkorytarzu.top"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "6414eebfabc4b2a3a74de10fd8d1cf0e7f8",
    "sha256": "1b96c806db210e7d3c70b9124a837d03c7ad6c4182f2a5805ac022976d59ff28",
    "subject": "gdzieswkorytarzu.top",
    "valid_to": "2027-01-02T06:45:33Z",
    "valid_from": "2026-10-04T06:45:34Z"
}
Registration record
{
    "registrar": "Dynadot LLC",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-06-04T07:20:39Z",
    "updated": "2026-06-04T07:24:00Z",
    "expires": "2027-06-04T07:20:39Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "adaline.ns.cloudflare.com",
        "logan.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-06-04T07:20:39Z",
        "last changed": "2026-06-04T07:24:00Z",
        "registration": "2026-06-04T07:20:39Z",
        "registrar expiration": "2027-06-04T07:20:39Z",
        "last update of RDAP database": "2026-10-16T07:12:51Z"
    }
}
Separate source record · 14 malicious + 4 suspicious / 92 · 2026-10-20 07:51: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-20T07:51:54Z
fetched_at
2026-10-27T20:27:02Z
stats
{"timeout":0,"harmless":42,"malicious":14,"suspicious":4,"undetected":32}

Cloudflare Radar

Malicious

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

f002e168-e051-44db-8fc5-0d17f208fc8c

Final URL

https://gdzieswkorytarzu.top/

HTTP response

200

Navigation history

  • URL
    https://gdzieswkorytarzu.top/
    Status
    200

DOM structure hash

06635c477af78420f92e95baa676308060d225f188fabe4701a4983c67892329

Document hash

c8322f5ca86ff3d8688744d5cda2e04510c2715194747295fefd077dff60beef

Domain risk categories

  • DGA Domains
  • Security threats
  • Malware
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    gdzieswkorytarzu.top
    Type
    A
    Value
    185.229.190.148
  • Name
    gdzieswkorytarzu.top
    Type
    AAAA
    Value
    2400:52e0:1e01::1445:1

DNSSEC valid

No

IP address

127.0.1.9

Verdict

Tags
  • dga domains
  • malware
Malicious
Yes
Categories
  • dga domains
  • malware

Registration record

Registrar
Dynadot LLC
Registered
Updated
Expires
Nameservers
  • adaline.ns.cloudflare.com.
  • logan.ns.cloudflare.com.
Original source fields · JSON
Uuid
f002e168-e051-44db-8fc5-0d17f208fc8c
Final url
https://gdzieswkorytarzu.top/
Status
200
History
[
    {
        "url": "https://gdzieswkorytarzu.top/",
        "status": 200
    }
]
DOM structure hash
06635c477af78420f92e95baa676308060d225f188fabe4701a4983c67892329
Document hash
c8322f5ca86ff3d8688744d5cda2e04510c2715194747295fefd077dff60beef
Domain risks
[
    "DGA Domains",
    "Security threats",
    "Malware",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "gdzieswkorytarzu.top",
        "type": "A",
        "value": "185.229.190.148"
    },
    {
        "name": "gdzieswkorytarzu.top",
        "type": "AAAA",
        "value": "2400:52e0:1e01::1445:1"
    }
]
Dnssec valid
false
Ip
127.0.1.9
Verdict
{
    "tags": [
        "dga domains",
        "malware"
    ],
    "malicious": true,
    "categories": [
        "dga domains",
        "malware"
    ]
}
Registration record
{
    "registrar": "Dynadot LLC",
    "created": "2026-06-04T07:20:39Z",
    "updated": "2026-06-04T07:24:00Z",
    "expires": "2027-06-04T07:20:39Z",
    "nameservers": [
        "adaline.ns.cloudflare.com.",
        "logan.ns.cloudflare.com."
    ]
}

URLScan

Malicious · engine verdict · score 92

Open report
URLScanOriginal source recordObserved: 17 fields

Observed: · Retrieved:

Report ID

019eb0c9-fcab-7359-aca2-05c5c80c36b5

Final URL

https://gdzieswkorytarzu.top/

HTTP response

404

Redirect type

https-only

Redirects

  • To
    https://gdzieswkorytarzu.top/
    From
    http://gdzieswkorytarzu.top/
    Status
    307

IP address

104.21.0.219

Contacted IP addresses

  • 104.21.0.219

Autonomous systems (ASN)

  • 13335

Document hash

ecf14b9ebe7061cddc7e2097a66c90692cc9c1d70d96b5f7ebdd14a0dbb61f54

TLS session and certificate

Subject alternative names
  • gdzieswkorytarzu.top
  • *.gdzieswkorytarzu.top
Cipher
AES_128_GCM
Issuer
WE1
Subject
gdzieswkorytarzu.top
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

6

Registered domain age, days

6

Certificate age, days

6

Certificate validity, days

90

Page requests

2

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
019eb0c9-fcab-7359-aca2-05c5c80c36b5
Final url
https://gdzieswkorytarzu.top/
Status
404
Redirected
https-only
Redirects
[
    {
        "to": "https://gdzieswkorytarzu.top/",
        "from": "http://gdzieswkorytarzu.top/",
        "status": 307
    }
]
Ip
104.21.0.219
Contacted IP addresses
[
    "104.21.0.219"
]
Asns
[
    "13335"
]
Document hash
ecf14b9ebe7061cddc7e2097a66c90692cc9c1d70d96b5f7ebdd14a0dbb61f54
Tls
{
    "san": [
        "gdzieswkorytarzu.top",
        "*.gdzieswkorytarzu.top"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "gdzieswkorytarzu.top",
    "protocol": "TLS 1.3",
    "valid_to": "2026-09-02T07:26:38Z",
    "valid_from": "2026-06-04T06:29:14Z"
}
Domain age days
6
Apex age days
6
Tls age days
6
Tls valid days
90
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 92,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
019eb0c9-fcab-7359-aca2-05c5c80c36b5
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

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 · 0 / 100 · 2026-10-27T20:33:02Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-27T20:33:02Z
source_timestamp
2026-10-27 21:33:02
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
gdzieswkorytarzu.top — Suspicious Domain
ai_description
PhishDestroy lists gdzieswkorytarzu.top as a suspicious domain after multiple engine detections, though no specific fraudulent activity was observed.
ai_generated_at
2026-10-27T20:31:03Z
ai_generated_by
threat-v3-groq
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.

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: 25 fields

Mail configuration

SPF lookups
0

CAA records

Domain
gdzieswkorytarzu.top

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

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

Crawler rules

User agents
  • *
Present
Yes

Page title and metadata

Page title
Привет Лось!
Indexing directives
noindex, nofollow

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
42
TLS
17
Waiting
223
Connection
7
Download
0
Response time, ms
289

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
264
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    172.64.33.198
    Host
    logan.ns.cloudflare.com
  • IP address
    172.64.34.224
    Host
    elisabeth.ns.cloudflare.com
DNS zone
gdzieswkorytarzu.top

Location

IP address
2400:52e0:1e00:2::1331:1
ASN
60068
Organization
Datacamp Limited
City
Frankfurt am Main
Country
DE

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
gdzieswkorytarzu.top

DNS records

A
  • 185.111.111.156
NS
  • elisabeth.ns.cloudflare.com
  • logan.ns.cloudflare.com
SOA
Primary nameserver
elisabeth.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418606446
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
TXT
  • yandex-verification=48f530d893b97af7
AAAA
  • 2400:52e0:1e00:2::1331:1

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
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2400:52e0:1e00:2::1331:1
IP version
6

Redirects

Redirect chain
  • https://gdzieswkorytarzu.top

Technology stack

Technologies
  • Cloudflare
  • Bunny

Registration record

Registrar
Dynadot LLC
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • adaline.ns.cloudflare.com
  • logan.ns.cloudflare.com

HTTP headers

Response headers
Server
BunnyCDN-DE1-1331
Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "gdzieswkorytarzu.top"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-27T19:50:38Z",
    "first": "2026-10-27T19:50:38Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 1370
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "Привет Лось!",
    "robots": "noindex, nofollow"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 42,
        "tls": 17,
        "wait": 223,
        "connect": 7,
        "download": 0
    },
    "response_ms": 289
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 264,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.33.198",
            "host": "logan.ns.cloudflare.com"
        },
        {
            "ip": "172.64.34.224",
            "host": "elisabeth.ns.cloudflare.com"
        }
    ],
    "zone": "gdzieswkorytarzu.top"
}
Location
{
    "ip": "2400:52e0:1e00:2::1331:1",
    "asn": "60068",
    "org": "Datacamp Limited",
    "city": "Frankfurt am Main",
    "country": "DE"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "gdzieswkorytarzu.top"
}
DNS records
{
    "A": [
        "185.111.111.156"
    ],
    "NS": [
        "elisabeth.ns.cloudflare.com",
        "logan.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"elisabeth.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418606446, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "TXT": [
        "yandex-verification=48f530d893b97af7"
    ],
    "AAAA": [
        "2400:52e0:1e00:2::1331:1"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "strict-origin-when-cross-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2400:52e0:1e00:2::1331:1",
    "family": 6
}
Redirects
{
    "chain": [
        "https://gdzieswkorytarzu.top"
    ]
}
Tech stack
{
    "technologies": [
        "Cloudflare",
        "Bunny"
    ]
}
Registration record
{
    "registrar": "Dynadot LLC",
    "created": "2026-06-04T07:20:39Z",
    "updated": "2026-06-04T07:24:00Z",
    "expires": "2027-06-04T07:20:39Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "adaline.ns.cloudflare.com",
        "logan.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "BunnyCDN-DE1-1331",
        "content-type": "text/html; charset=utf-8",
        "x-content-type-options": "nosniff",
        "referrer-policy": "strict-origin-when-cross-origin"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
DGA Domains Security threats Malware Dga domains Malware
View full Cloudflare Radar report

Questions about gdzieswkorytarzu.top

Is gdzieswkorytarzu.top legit?

No. PhishDestroy classifies gdzieswkorytarzu.top as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-27. VirusTotal: 18/92 engines flag it. Treat the site as unsafe.

Is gdzieswkorytarzu.top safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on gdzieswkorytarzu.top. 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 gdzieswkorytarzu.top?

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 · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded
StateStored capture
HTTP status404
Final URLhttps://gdzieswkorytarzu.top/
Position1 / 4
Open capture Wayback Download
All capture links and hashes (4)
Observed page title
Привет Лось!
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 66 days
gdzieswkorytarzu.top: caution — 18/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card gdzieswkorytarzu.top: caution — 18/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v eb0d5c1b39be

Domain details

Domain
IP Context Germany195.181.166.158 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contact["abuse@dynadot.com", "f651612a2f356ad3s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for gdzieswkorytarzu.top →
RegistrationCreated Jun 4, 2026 (145d) — Expires Jun 4, 2027
Registrant countryUnited States VirusTotal WHOIS
Registrant1f8f4166599d23eef651612a2f356ad3s@ VirusTotal WHOIS
WHOIS statusclientTransferProhibited
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 27, 2026
DOM Analysisanalyzed Oct 27, 2026score 98/100
Submitted URLhttp://gdzieswkorytarzu.top/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Germany195.181.166.158
Network ASN
AS60068
Organization
Datacamp Limited
Observed location
GermanyFrankfurt am Main, DE
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • adaline.ns.cloudflare.com
  • logan.ns.cloudflare.com

SOA

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

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-04 06:45:34
Valid until
2027-01-02 06:45:33
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1b96c806db210e7d3c70b9124a837d03c7ad6c4182f2a5805ac022976d59ff28
Certificate names · 1 SAN
  • gdzieswkorytarzu.top

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

viewdns.info · 195.181.166.158rapiddns.io
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

18 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 18 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of gdzieswkorytarzu.top · checked Oct 27, 2026

100
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
0.76 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.76 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://gdzieswkorytarzu.top/
Привет Лось!
Response
HTTP 200
HTML body
264 B
Compressed
219 B
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: BunnyCDN-NY1-1313
Cache-Control: public, max-age=0, must-revalidate
Content-Encoding: gzip
Security headers present
X-Content-Type-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: c8322f5ca86ff3d8688744d5cda2e04510c2715194747295fefd077dff60beef
Saved response-header values · 25
Access-Control-Allow-Origin
*
Cache-Control
public, max-age=0, must-revalidate
CDN-Cache
MISS
CDN-CachedAt
10/27/2026 19:54:53
CDN-EdgeStorageId
1313
CDN-ProxyVer
1.71
CDN-PullZone
6775086
CDN-RequestCountryCode
US
CDN-RequestId
e393ee13976f42b00b82c5ea3d2ebe13
CDN-RequestPullCode
200
CDN-RequestPullSuccess
True
CDN-RequestTime
0
CDN-Status
200
cf-ray
a51441548c30cdf0-EWR
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Tue, 27 Oct 2026 19:54:53 GMT
nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Referrer-Policy
strict-origin-when-cross-origin
report-to
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=6W1RE1R32dDrT%2Ba%2FTKx%2B9RaqcCAnGLFj%2FK1muclO4epUfoAWqgntgkaEjraFQPTRpsFdYBtKS76mzWzKyZ1HO27MY1K72jBEZWZ2DG9om6Z9O1lroJHib5E6U%2B%2FPnrGG6J1
Server
BunnyCDN-NY1-1313
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-Content-Type-Options
nosniff

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

Archived
All retained availability observations1

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

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 20:59:30.394080
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · 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: 1 of 1
  • Threat Ingested
    gdzieswkorytarzu.top detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 92
  • 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: 18/92
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as DGA Domains, Security threats, malware
  • 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. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    18/92 engine detections

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    gdzieswkorytarzu.top

    View source
  5. URLScan

    Malicious · engine verdict · score 92

    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.

gdzieswkorytarzu.top

Evidence & External Reports

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

Were You Affected by This Site?

4 evidence signal groups linked 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.

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 →.

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

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