Skip to security report
Analytics Dashboard
polnexis.shop — PhishDestroy
VirusTotal: result unavailable for this observation. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
polnexis.shop favicon

polnexis.shop

In short

PhishDestroy stores a record for polnexis.shop. Source observations are dated separately; missing checks do not establish safety.

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Netherlands185.62.56.121Snel
Registered
Apr 19, 2026
First observed
Nov 4, 2026
PhishDestroy assessment Medium
25/100
Evidence score
Availability Last known active Latest stored reachability observation Observed URLScan
Risk signals
Stored PhishDestroy threat listing
URLScan
Malicious
engine verdict · score 97
Page captures
3
open gallery
Domain age
199 days
registered 2026-04-19 according to WHOIS
Nov 4, 2026
X Telegram API

Analysis

Medium
Status
Last known active
Hosting
Netherlands185.62.56.121Snel
Registrar
United StatesDynadot
Registered
Apr 19, 2026
Page captures
3
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for polnexis.shop. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidence 2 sources

URLScan

Malicious · engine verdict · score 97

SHA-256 aa66817fe6343b94c3d64c8909dd4450b64d7ccfbd3511e3da477d4b6a523197

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

019f8946-d8e6-77bc-bf23-5a34c13b7d03

Final URL

https://polnexis.shop/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://polnexis.shop/
    From
    http://polnexis.shop/
    Status
    307

IP address

185.62.56.121

Contacted domains

  • cdn.jsdelivr.net
  • fonts.gstatic.com
  • cdnjs.cloudflare.com
  • www.cloudflare.com
  • fonts.googleapis.com

Contacted IP addresses

  • 104.16.123.96
  • 104.17.207.5
  • 142.251.13.94
  • 104.17.25.14
  • 192.178.170.95
  • 185.62.56.121

Autonomous systems (ASN)

  • 13335
  • 15169
  • 62370

Server countries

  • US
  • NL

Document hash

aa66817fe6343b94c3d64c8909dd4450b64d7ccfbd3511e3da477d4b6a523197

Script hashes

  • e776c8e03ae39686bf5344edf2667ee34a517077e47c1b709c3cc2c8dd1792c3

JavaScript globals

  • toggleTermsPopup
  • intlTelInput
  • __visitorCountry
  • FingerprintJS

Browser storage keys

  • t_fingerprint

TLS session and certificate

Subject alternative names
  • polnexis.shop
Cipher
AES_128_GCM
Issuer
ZeroSSL ECC DV SSL CA 2
Subject
polnexis.shop
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

94

Registered domain age, days

94

Certificate age, days

1

Certificate validity, days

90

Page requests

21

Provider verdicts

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

HTTP headers

Content-type
text/html; charset=utf-8
Referrer-policy
no-referrer-when-downgrade
Original source fields · JSON
Uuid
019f8946-d8e6-77bc-bf23-5a34c13b7d03
Final url
https://polnexis.shop/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://polnexis.shop/",
        "from": "http://polnexis.shop/",
        "status": 307
    }
]
Ip
185.62.56.121
Contacted domains
[
    "cdn.jsdelivr.net",
    "fonts.gstatic.com",
    "cdnjs.cloudflare.com",
    "www.cloudflare.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "104.16.123.96",
    "104.17.207.5",
    "142.251.13.94",
    "104.17.25.14",
    "192.178.170.95",
    "185.62.56.121"
]
Asns
[
    "13335",
    "15169",
    "62370"
]
Countries
[
    "US",
    "NL"
]
Document hash
aa66817fe6343b94c3d64c8909dd4450b64d7ccfbd3511e3da477d4b6a523197
Script hashes
[
    "e776c8e03ae39686bf5344edf2667ee34a517077e47c1b709c3cc2c8dd1792c3"
]
Globals
[
    "toggleTermsPopup",
    "intlTelInput",
    "__visitorCountry",
    "FingerprintJS"
]
Storage keys
[
    "t_fingerprint"
]
Tls
{
    "san": [
        "polnexis.shop"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "ZeroSSL ECC DV SSL CA 2",
    "subject": "polnexis.shop",
    "protocol": "TLS 1.3",
    "valid_to": "2026-10-19T23:59:59Z",
    "valid_from": "2026-07-21T00:00:00Z"
}
Domain age days
94
Apex age days
94
Tls age days
1
Tls valid days
90
Requests
21
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "referrer-policy": "no-referrer-when-downgrade"
}

Spamhaus DBL

Check recorded; verdict not retained

Open report

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

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 3 captures

URLScan · 2026-07-22 1 / 3
SourceURLScan · 2026-07-22
Recorded
StateStored capture
HTTP status200
Final URLhttps://polnexis.shop/
Position1 / 3
Open capture Source Report Wayback Download
All capture links and hashes (3)
TLS Certificate
Issued by ZeroSSL ECC DV SSL CA 2

Domain details

Domain
IP Reputation Netherlands185.62.56.121 abuse score 0/100 0 reports checked Nov 4, 2026
Registrar Dynadot US(US)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for polnexis.shop →
RegistrationCreated Apr 19, 2026 (199d)
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedNov 4, 2026
Submitted URLhttp://polnexis.shop/
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

Resolved IP
Netherlands185.62.56.121
Network ASN
AS62370
Organization
Snel
Observed location
NetherlandsRotterdam, NL

Nameservers 1

  • nataly.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
ZeroSSL ECC DV SSL CA 2
Valid from
2026-07-21 00:00:00
Valid until
2026-10-19 23:59:59
Hostname coverage
Stored certificate expired or unverified
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate names · 1 SAN
  • polnexis.shop

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

viewdns.info · 185.62.56.121rapiddns.io
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive
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://polnexis.shop/
Final URL: https://polnexis.shop/
PolNexis | AI Trading Platform | Oficjalna Strona
PolNexis oferuje wsparcie handlowe z wykorzystaniem AI, zautomatyzowane boty, strukturalne kontrole ryzyka i przejrzyste operacje, umożliwiające świadome wykonywanie transakcji.
Response
HTTP 200
HTML body
44.4 KB
Compressed
12.0 KB
Links
29 internal · 0 external
Selected response headers
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Security headers present
Referrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: PolNexis AI-Driven Trading Automation Platform
Open Graph description: PolNexis delivers AI-enhanced trading support with automated bots, structured risk controls, and transparent operations for informed execution.
Twitter card: summary
Saved response-header values · 9
Alt-Svc
h3=":443"; ma=2592000
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Wed, 04 Nov 2026 19:37:09 GMT
Etag
"dm9jpyp7sjjnz29-gzip"
Last-Modified
Tue, 20 Oct 2026 09:08:30 GMT
Referrer-Policy
no-referrer-when-downgrade
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Archived

Captured network requests

Network requests: 21 SHA-256 hashes: 20 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-04 19:25 UTC.

Open this scan on URLScan 019f8946-d8e6-77bc-bf23-5a34c13b7d03 ↗

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-11-02 04:28:06
All retained availability observations1

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

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 20:25:52.857956
    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: 6. 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
    polnexis.shop detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · Forensic Evidence Collected Recorded: 4 of 4
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 97
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
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

3 entries
  1. Wayback Machine

    Page archived

    View source
  2. Added to PhishDestroy

    polnexis.shop

    View source
  3. URLScan

    Malicious · engine verdict · score 97

    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
All stored records by source

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

Download all records as JSON

Check for cloaking

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

polnexis.shop

Evidence & External Reports

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

Were You Affected by This Site?

3 evidence signal groups linked 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 polnexis.shop)
  • 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.

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