Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 0/92 engines flagged. malicious: 0. suspicious: 0. Analysis time (as stored): 2026-09-06T14:30:12Z. Retrieved (as stored): 2026-10-29T12:02:51Z. Listed by external blocklists: MetaMask, SEAL. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
piteas.pro favicon

piteas.pro

In short

The captured piteas.pro page presents itself as "Pulsechain's leading DEX aggregator," with a headline claiming 3M+ swaps, $4B+ total routed volume, and 100K+ users. The main interaction is a swap panel defaulting to PLS and PTS amounts, with a "Connect Wallet" button as the primary action and a "Paste CA" option above the fields. A banner below the panel states that PTS is now deflationary, with treasury revenue used to buy and burn tokens.

“Piteas | Pulsechain Dex Aggregator”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
United Kingdom188.114.96.9CloudFLARENET-EU · CDN
Registered
Sep 3, 2026
First observed
Oct 29, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
Stored blocklist matches: 2
VirusTotal
0 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
OTX
3
community references
URLScan
Malicious
Page captures
2
open gallery
Domain age
62 days
registered 2026-09-03 according to WHOIS
OTX: 3 refs Oct 29, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded piteas.pro on 2026-10-29. Stored VirusTotal result: 0/92 engines flagged. malicious: 0. suspicious: 0. Analysis time (as stored): 2026-09-06T14:30:12Z. Retrieved (as stored): 2026-10-29T12:02:51Z. Listed by external blocklists: MetaMask, SEAL. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: CloudFLARENET-EU. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
0 / 92
Blocklist matches
2
Scam type (automated label)
Crypto Drainer
Hosting
United Kingdom188.114.96.9CloudFLARENET-EU · CDN
Registrar
United StatesDynadot
Registered
Sep 3, 2026
OTX
3 community refs
Page captures
2
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-10-29T12:02:58Z
SHA-256: b626b260a31645840635e4fb2c3d3ffdab795ccc3e072f621125431811720f28

PhishDestroy analysis, reviewed version

The captured piteas.pro page presents itself as "Pulsechain's leading DEX aggregator," with a headline claiming 3M+ swaps, $4B+ total routed volume, and 100K+ users. The main interaction is a swap panel defaulting to PLS and PTS amounts, with a "Connect Wallet" button as the primary action and a "Paste CA" option above the fields. A banner below the panel states that PTS is now deflationary, with treasury revenue used to buy and burn tokens.

VirusTotal's domain-scoped analysis of piteas.pro returned 0 detections out of 92 engines, with no engines flagging it as malicious or suspicious.

Source evidenceVirusTotal 0 / 92 · OTX 3 references 8 sources

URLScan

Malicious

SHA-256 819f82d2712f87bbea5a5c27b19d8e35b2b966e8e0afd46d3e2f5ba2541e7b31

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a1876c-dd5f-715b-a2ff-fb3dab78a0bb

Final URL

https://piteas.pro/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://piteas.pro/
    From
    http://piteas.pro/
    Status
    307

IP address

104.21.22.102

Contacted domains

  • fonts.gstatic.com
  • cdn.tailwindcss.com
  • static.cloudflareinsights.com
  • raw.githubusercontent.com
  • fonts.googleapis.com

Contacted IP addresses

  • 142.251.222.227
  • 104.16.80.73
  • 185.199.110.133
  • 142.251.222.10
  • 104.26.2.143
  • 104.21.22.102

Autonomous systems (ASN)

  • 15169
  • 13335
  • 54113

Server countries

  • US

Document hash

9e712a99c943ff237c5250cc4769dc115a0aecf9201c2eff38670c1ba447f7b2

JavaScript globals

  • tailwind
  • /template.html
  • sanitizeDecimal
  • __cfBeacon
  • PLS_TO_PTS_RATE
  • plsInput
  • ptsInput

TLS session and certificate

Subject alternative names
  • piteas.pro
  • *.piteas.pro
Cipher
AES_128_GCM
Issuer
WE1
Subject
piteas.pro
Protocol
QUIC
Valid until
Valid from

Domain age, days

55

Registered domain age, days

55

Certificate age, days

55

Certificate validity, days

90

Page requests

10

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
99
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • pulsechain
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Pulsechain
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
cloudflare
Content-type
text/html
Priority
u=0,i
Original source fields · JSON
Uuid
01a1876c-dd5f-715b-a2ff-fb3dab78a0bb
Final url
https://piteas.pro/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://piteas.pro/",
        "from": "http://piteas.pro/",
        "status": 307
    }
]
Ip
104.21.22.102
Contacted domains
[
    "fonts.gstatic.com",
    "cdn.tailwindcss.com",
    "static.cloudflareinsights.com",
    "raw.githubusercontent.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.251.222.227",
    "104.16.80.73",
    "185.199.110.133",
    "142.251.222.10",
    "104.26.2.143",
    "104.21.22.102"
]
Asns
[
    "15169",
    "13335",
    "54113"
]
Countries
[
    "US"
]
Document hash
9e712a99c943ff237c5250cc4769dc115a0aecf9201c2eff38670c1ba447f7b2
Globals
[
    "tailwind",
    "/template.html",
    "sanitizeDecimal",
    "__cfBeacon",
    "PLS_TO_PTS_RATE",
    "plsInput",
    "ptsInput"
]
Tls
{
    "san": [
        "piteas.pro",
        "*.piteas.pro"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "piteas.pro",
    "protocol": "QUIC",
    "valid_to": "2026-12-03T10:58:11Z",
    "valid_from": "2026-09-04T09:58:14Z"
}
Domain age days
55
Apex age days
55
Tls age days
55
Tls valid days
90
Requests
10
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "pulsechain"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Pulsechain"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html",
    "priority": "u=0,i"
}
Separate monitor record · 2026-10-30 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1876c-dd5f-715b-a2ff-fb3dab78a0bb
score
100
malicious
true
result_at
2026-10-30T04:30:24Z
enriched_at
2026-10-30T09:11:48Z
source_timestamps
{"urlscan_result_at":"2026-10-30 05:30:24","urlscan_enriched_at":"2026-10-30 10:11:48"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

VirusTotal

0 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
0
Suspicious
0
Undetected
37

Reputation score

0

First seen

DNS records

  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    hope.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    hope.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3037::ac43:cc2e
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.22.102
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.204.46
  • TTL, seconds
    21600
    Type
    NS
    Value
    venkat.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3033::6815:1666

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • piteas.pro
  • *.piteas.pro
Issuer
Google Trust Services / WE1
Serial
6a43e99db27dc08d13164a2a00176d57
SHA-256
ffffd9e92a57bfb3f5cd8a053475cedb54795f40ef72ae9e71f4e99f37f76028
Subject
piteas.pro
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
  • add period
Registry events
Expiration
Last changed
Registration
Last RDAP database update
Registrar
Dynadot Inc
Registrar IANA ID
472
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 37
}
Reputation
0
First seen
2026-09-04T11:30:42Z
DNS records
[
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "hope.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "hope.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::ac43:cc2e"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.22.102"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.204.46"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "venkat.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::6815:1666"
    }
]
Dns at
2026-09-06T14:31:46Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "piteas.pro",
        "*.piteas.pro"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "6a43e99db27dc08d13164a2a00176d57",
    "sha256": "ffffd9e92a57bfb3f5cd8a053475cedb54795f40ef72ae9e71f4e99f37f76028",
    "subject": "piteas.pro",
    "valid_to": "2026-12-03T10:58:11Z",
    "valid_from": "2026-09-04T09:58:14Z"
}
Registry data
{
    "status": [
        "client transfer prohibited",
        "add period"
    ],
    "events": {
        "expiration": "2027-09-03T22:36:41Z",
        "last changed": "2026-09-04T10:41:03Z",
        "registration": "2026-09-03T22:36:41Z",
        "last update of RDAP database": "2026-09-04T11:30:41Z"
    },
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472"
}
Separate collector summary

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

source
VirusTotal
scope
unknown
result_state
observed
numerator
10
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","CRDF","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","Kaspersky","Seclookup","Webroot"]
observed_at
null
checked_at
2026-11-02 04:01:20
fetched_at
2026-11-02 03:01:21
time_basis
as stored; legacy timezone not established

OTX

3 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Report ID

06cd0c98-c687-4f03-95f3-2b931305d6c7

Final URL

https://piteas.pro/

HTTP response

200

Navigation history

  • URL
    https://piteas.pro/
    Status
    200

DOM structure hash

7d090f668c35cdfcc676c0d2ccada503457d8141028ff5ea77ab7a493144a6e9

Document hash

9e712a99c943ff237c5250cc4769dc115a0aecf9201c2eff38670c1ba447f7b2

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    piteas.pro
    Type
    A
    Value
    104.21.22.102
  • Name
    piteas.pro
    Type
    A
    Value
    172.67.204.46
  • Name
    piteas.pro
    Type
    AAAA
    Value
    2606:4700:3033::6815:1666
  • Name
    piteas.pro
    Type
    AAAA
    Value
    2606:4700:3037::ac43:cc2e

DNSSEC valid

No

IP address

127.0.1.20

127.0.1.20 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
06cd0c98-c687-4f03-95f3-2b931305d6c7
Final url
https://piteas.pro/
Status
200
History
[
    {
        "url": "https://piteas.pro/",
        "status": 200
    }
]
DOM structure hash
7d090f668c35cdfcc676c0d2ccada503457d8141028ff5ea77ab7a493144a6e9
Document hash
9e712a99c943ff237c5250cc4769dc115a0aecf9201c2eff38670c1ba447f7b2
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "piteas.pro",
        "type": "A",
        "value": "104.21.22.102"
    },
    {
        "name": "piteas.pro",
        "type": "A",
        "value": "172.67.204.46"
    },
    {
        "name": "piteas.pro",
        "type": "AAAA",
        "value": "2606:4700:3033::6815:1666"
    },
    {
        "name": "piteas.pro",
        "type": "AAAA",
        "value": "2606:4700:3037::ac43:cc2e"
    }
]
Dnssec valid
false
Ip
127.0.1.20

127.0.1.20 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

5 / 100 · heuristic score · 0 brand references · 1 classification

Open report
Separate monitor score · 5 / 100 · 2026-10-29T12:08:57Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
5
analyzed_at
2026-10-29T12:08:57Z
source_timestamp
2026-10-29 13:08:57
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
piteas.pro — Pulsechain DEX aggregator swap page
ai_description
The captured piteas.pro page shows a Pulsechain DEX aggregator swap panel, and PhishDestroy records a VirusTotal domain scan with no detections.
ai_summary
The captured piteas.pro page presents itself as "Pulsechain's leading DEX aggregator," with a headline claiming 3M+ swaps, $4B+ total routed volume, and 100K+ users. The main interaction is a swap panel defaulting to PLS and PTS amounts, with a "Connect Wallet" button as the primary action and a "Paste CA" option above the fields. A banner below the panel states that PTS is now deflationary, with treasury revenue used to buy and burn tokens. VirusTotal's domain-scoped analysis of piteas.pro returned 0 detections out of 92 engines, with no engines flagging it as malicious or suspicious.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-29 13:03:53
revision
b0309a94660a74af5d8c664664829406f0b3b867aea75f6ab7e64b2fc6a29b07
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: 25 fields

Mail configuration

SPF lookups
0

CAA records

Domain
piteas.pro

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

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

Crawler rules

User agents
  • *
  • Amazonbot
  • Applebot-Extended
  • Bytespider
  • CCBot
Present
Yes

Sitemap

Present
Yes
URL count
2

Page title and metadata

Page title
Piteas | Pulsechain Dex Aggregator

Trackers

Requests
8
Observed services
  • Name
    GitHub
    Company
    GitHub, Inc.
    Country
    US
    Category
    Customer Interaction
    Requests
    1
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    3

Forms and mixed content

Scripts without SRI
  • https://cdn.tailwindcss.com/
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
8
TLS
93
Waiting
129
Connection
34
Download
0
Response time, ms
264

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
  • 8080

Carbon estimate

Bytes
16481
CO₂, grams
0.0006
Cleaner than, %
61

DNS servers

Nameservers
  • IP address
    162.159.44.254
    Host
    venkat.ns.cloudflare.com
  • IP address
    173.245.58.163
    Host
    hope.ns.cloudflare.com
DNS zone
piteas.pro

Location

IP address
2a06:98c1:3121::9
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Google Trust Services / WE1
Subject
piteas.pro

DNS records

A
  • 188.114.96.9
  • 188.114.97.9
NS
  • hope.ns.cloudflare.com
  • venkat.ns.cloudflare.com
SOA
Primary nameserver
hope.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2414187958
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2a06:98c1:3120::9
  • 2a06:98c1:3121::9

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

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3120::9
IP version
6

Redirects

Redirect chain
  • https://piteas.pro

Page links

Internal links
2

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "piteas.pro"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-29T11:33:53Z",
    "first": "2026-10-29T11:33:53Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 5375
}
Crawler rules
{
    "agents": [
        "*",
        "Amazonbot",
        "Applebot-Extended",
        "Bytespider",
        "CCBot"
    ],
    "present": true
}
Sitemap
{
    "present": true,
    "url_count": 2
}
Page title and metadata
{
    "title": "Piteas | Pulsechain Dex Aggregator"
}
Trackers
{
    "requests": 8,
    "trackers": [
        {
            "name": "GitHub",
            "company": "GitHub, Inc.",
            "country": "US",
            "category": "Customer Interaction",
            "requests": 1
        },
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 3
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://cdn.tailwindcss.com/"
    ],
    "third_party_scripts": 1
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 8,
        "tls": 93,
        "wait": 129,
        "connect": 34,
        "download": 0
    },
    "response_ms": 264
}
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,
        8080
    ]
}
Carbon
{
    "bytes": 16481,
    "co2_grams": 0.0006,
    "cleaner_than": 61
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.44.254",
            "host": "venkat.ns.cloudflare.com"
        },
        {
            "ip": "173.245.58.163",
            "host": "hope.ns.cloudflare.com"
        }
    ],
    "zone": "piteas.pro"
}
Location
{
    "ip": "2a06:98c1:3121::9",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "piteas.pro"
}
DNS records
{
    "A": [
        "188.114.96.9",
        "188.114.97.9"
    ],
    "NS": [
        "hope.ns.cloudflare.com",
        "venkat.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"hope.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2414187958, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2a06:98c1:3120::9",
        "2a06:98c1:3121::9"
    ]
}
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
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3120::9",
    "family": 6
}
Redirects
{
    "chain": [
        "https://piteas.pro"
    ]
}
Page links
{
    "internal_count": 2
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html"
    }
}

Questions about piteas.pro

Is piteas.pro legit?

PhishDestroy rates piteas.pro as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-10-29. Stored VirusTotal result: 0/92 engines flagged. malicious: 0. suspicious: 0. Analysis time (as stored): 2026-09-06T14:30:12Z. Retrieved (as stored): 2026-10-29T12:02:51Z. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is piteas.pro safe to connect a wallet?

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

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

Extracted from stored page analysis

Observed indicators

1 wallet · 0 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

ETH
0xA1077a294dDE1B09bB078844df40758a5D0f9a27Format validated · Domain analysis

IoC extraction recorded 2026-10-30 05:00:18 UTC

Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 2 captures

Cloudflare Radar 1 / 2 Used in the analysis Source file SHA-256: b626b260a31645840635e4fb2c3d3ffdab795ccc3e072f621125431811720f28 SHA-256 of the prepared copy given to the model: c49bee4f81b58ecccaa0fc0ef7c54ae49c0c795b0788da89fa357865b8057a47
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://piteas.pro/
Position1 / 2
Open capture Source Report Wayback Download
All capture links and hashes (2)
piteas.pro: Crypto scam — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 66/100 (high).
Social preview card piteas.pro: Crypto scam — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 66/100 (high). v 42f36667f695

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Pulsechain report ↗
Observed indicators1 wallet · 0 Telegram — full values ↗
IP Context United Kingdom188.114.96.9 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contactabuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for piteas.pro →
RegistrationCreated Sep 3, 2026 (62d · New) — Expires Sep 3, 2027
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 29, 2026
DOM Analysisanalyzed Oct 29, 2026score 5/100
IoC Extractionscanned Oct 30, 20261 wallet · 0 Telegram IoC
Submitted URLhttp://piteas.pro/
Favicon Hash
Observed page title
Piteas | Pulsechain Dex Aggregator
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 28 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom188.114.96.9
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • hope.ns.cloudflare.com
  • venkat.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-04 09:58:14
Valid until
2026-12-03 10:58:11
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintffffd9e92a57bfb3f5cd8a053475cedb54795f40ef72ae9e71f4e99f37f76028
Certificate names · 2 SANs
  • piteas.pro
  • *.piteas.pro

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

viewdns.info · 188.114.96.9rapiddns.io

Latest Classified Outcome 2026-11-04 11:01:00 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-04 11:01:00 UTC
RDAP registration
Observed timeline last reachable: 2026-11-04 11:01:00 UTC last content: 2026-11-04 11:01:00 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of piteas.pro · checked Oct 29, 2026

89
Needs Work
Performance
FCP
2.93 s
First Contentful Paint
LCP
2.93 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
3.19 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://piteas.pro/
Piteas | Pulsechain Dex Aggregator
Response
HTTP 200
HTML body
16.5 KB
Compressed
4.2 KB
Links
13 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
CF-Cache-Status: HIT
Cache-Control: public, max-age=0, must-revalidate
Content-Encoding: gzip
Server: cloudflare
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 13
alt-svc
h2=":443"; ma=60
Cache-Control
public, max-age=0, must-revalidate
CF-Cache-Status
HIT
CF-RAY
a521dd1f3e64aded-EWR
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Thu, 29 Oct 2026 11:33:09 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=JcNk15HW5d%2FNkvx9LocjdiIKAZ7eeRz6e0%2FWtsNBSlws2fDbEwQTkKEXXp74nU%2BgmWCcE48yu%2BWzh2goXE0zyXEc7ti7T2q7g46QNV15wQR5chQjwjrmwrB%2Boeq7"}]}
Server
cloudflare
Server-Timing
cfCacheStatus;desc="HIT"
Transfer-Encoding
chunked

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 10 SHA-256 hashes: 10 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-10-29 11:32 UTC.

Open this scan on URLScan 01a1876c-dd5f-715b-a2ff-fb3dab78a0bb ↗

Stored observation history7

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

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

Earlier observations 2
  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability observations27

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

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 12:01:00.000000
    Evidence SHA-256
    1575ede733fb230646366f766729b9cd8cd290b79703a1b74e97706c83cb9b28
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 12:01:00
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 12:01:00.000000
    Evidence SHA-256
    1575ede733fb230646366f766729b9cd8cd290b79703a1b74e97706c83cb9b28
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 12:01:00
    Evidence reason
    alive_content
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-03 23:21:00.551669
    Evidence SHA-256
    93de4ce3edcedd421525733b44961d482bf295f4b8d35b7851f110ca6f86698b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 23:21:00.551669
    Evidence reason
  4. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 23:20:40.877283
    Evidence SHA-256
    25c5ac0172f94ac6589ba15d57bef64f7b2aa3a7f5fe700edf28b10d7afed8a7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 23:20:40.877283
    Evidence reason
  5. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:32:07.000000
    Evidence SHA-256
    58a4e0673485f1f491d0efc5c245b1d386cf80b2c161f85645dcb9926bea8112
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:32:07
    Evidence reason
    alive_content
  6. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    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-02 12:32:07.000000
    Evidence SHA-256
    f806f65c215de99b99097814ba718bc08f64fab62c9556481236a2447370d7cc
    Evidence timestamp as recorded
    2026-11-02 12:32:07
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  7. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:34:08.000000
    Evidence SHA-256
    fa09a1296f42c719232cd2e34d13abeabb1bd6b473af0f1bb38f019122252c39
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:34:08
    Evidence reason
    alive_content
  8. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:34:08.000000
    Evidence SHA-256
    fa09a1296f42c719232cd2e34d13abeabb1bd6b473af0f1bb38f019122252c39
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:34:08
    Evidence reason
    alive_content
  9. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 23:20:11.055498
    Evidence SHA-256
    7c023747294077bd6e2ec2b080dc137e75a3ed6faf38dbdfcaa23e6958793fa3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:20:11.055498
    Evidence reason
  10. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:36:07.000000
    Evidence SHA-256
    5ede2b78fa64e84ce793801b713520daaa76f65b70392d61e7b42e5d11cb3edb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:36:07
    Evidence reason
    alive_content
  11. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:36:07.000000
    Evidence SHA-256
    5ede2b78fa64e84ce793801b713520daaa76f65b70392d61e7b42e5d11cb3edb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:36:07
    Evidence reason
    alive_content
  12. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:23:47.000000
    Evidence SHA-256
    df1454d83c5de77e1b3b24a33207b8c43256069c36f3ea44f4fdd40309ca7862
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:23:47
    Evidence reason
    alive_content
  13. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:23:47.000000
    Evidence SHA-256
    df1454d83c5de77e1b3b24a33207b8c43256069c36f3ea44f4fdd40309ca7862
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:23:47
    Evidence reason
    alive_content
  14. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:20:09.600237
    Evidence SHA-256
    fdac094cb4b92350d9f20b2c0fc69fdcaa33e7da7eb2d1063ea3f2bc257f29ef
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
    Evidence reason
  15. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:35:53.000000
    Evidence SHA-256
    1e36cd4d73ca1314a945d722d7f4c0f874b6fb34b68c68e1b5f44e20189ecddb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:35:53
    Evidence reason
    alive_content
  16. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:35:53.000000
    Evidence SHA-256
    1e36cd4d73ca1314a945d722d7f4c0f874b6fb34b68c68e1b5f44e20189ecddb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:35:53
    Evidence reason
    alive_content
  17. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:56:00.000000
    Evidence SHA-256
    aef97e3c6264eed09ff595d893a0a873460e4e44f37057ab9fd634af812df695
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:56:00
    Evidence reason
    alive_content
  18. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:56:00.000000
    Evidence SHA-256
    aef97e3c6264eed09ff595d893a0a873460e4e44f37057ab9fd634af812df695
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:56:00
    Evidence reason
    alive_content
  19. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:26:55.000000
    Evidence SHA-256
    276931fe94a038e17cb08273537a5f544f670c2e954028619676f35183983177
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:26:55
    Evidence reason
    alive_content
  20. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:26:55.000000
    Evidence SHA-256
    276931fe94a038e17cb08273537a5f544f670c2e954028619676f35183983177
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:26:55
    Evidence reason
    alive_content
  21. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 22:35:15.875079
    Evidence SHA-256
    97b1f1aad91757df55a07aa8eadffa1ea48bf460a07a53a1e786c935a601fca5
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 22:35:15.875079
    Evidence reason
  22. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:34:27.000000
    Evidence SHA-256
    28bcbc9ada0fba8e50ff47085f0e1f488c7595c283b1d2768441130df60bc8ee
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:34:27
    Evidence reason
    alive_content
  23. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:34:27.000000
    Evidence SHA-256
    28bcbc9ada0fba8e50ff47085f0e1f488c7595c283b1d2768441130df60bc8ee
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:34:27
    Evidence reason
    alive_content
  24. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:33:47.000000
    Evidence SHA-256
    23147fe52244f9630657840f086e7064102067f75393b1794910bc4d5ee86369
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:33:47
    Evidence reason
    alive_content
  25. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:33:47.000000
    Evidence SHA-256
    23147fe52244f9630657840f086e7064102067f75393b1794910bc4d5ee86369
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:33:47
    Evidence reason
    alive_content
  26. 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-10-29 12:32:25.000000
    Evidence SHA-256
    2a0432e11d1e3363b4c6d0e2a19a58973764b07b8fa97df2455c302c70c1da41
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:32:25
    Evidence reason
  27. 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-10-29 12:32:25.000000
    Evidence SHA-256
    2a0432e11d1e3363b4c6d0e2a19a58973764b07b8fa97df2455c302c70c1da41
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:32:25
    Evidence reason

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
    piteas.pro detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Blocklist Detection · OTX Community References · Automated brand label: Pulsechain · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • 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
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • Automated brand label: Pulsechain
    Collector label, not confirmed by a page check.
  • 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. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    piteas.pro

    View source
  4. URLScan

    Page captured

    View source
  5. VirusTotal

    0/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
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.

piteas.pro

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report 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?

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