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

payutech.pro

In short

The captured payutech.pro page presents a single centered login card on a plain light background, headed simply "Login". It asks for a username and a password in two labeled text fields, followed by a dark Login button that submits the credentials. No branding, logo or supporting text appears alongside the form, so the page's only visible purpose is collecting account credentials.

“Login”

Review the evidence
Registrar
IndiaPDR
Resolved IP
Switzerland209.99.189.113HostRoyale Technologies
Registered
Nov 23, 2024
First observed
Nov 2, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed Cloudflare Radar · HTTP 200
Risk signals
VirusTotal detections: 14/92 Spamhaus DBL: spam domain
VirusTotal
14 / 92
engine detections ·
OTX
6
community references
URLScan
Malicious
engine verdict · score 92
Cloudflare Radar
Phishing
Page captures
8
open gallery
Domain age
708 days
registered 2024-11-23 according to WHOIS
OTX: 6 refs Nov 2, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded payutech.pro on 2026-11-02. VirusTotal: 14/92 engines flag it. Listed on Spamhaus DBL. Risk: critical (100/100). Registrar: PDR. Status: Last known active. Hosting: SKN Subnet & Telecom Ltd. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
14 / 92
Hosting
Switzerland209.99.189.113HostRoyale Technologies
Registrar
IndiaPDR
Registered
Nov 23, 2024
OTX
6 community refs
Page captures
8
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-11-02T03:33:17Z
SHA-256: f4212d7d7e5edaf712d770a367864b331df92f9dcb94dfffc0d5bfa4649656a1

PhishDestroy analysis, reviewed version

The captured payutech.pro page presents a single centered login card on a plain light background, headed simply "Login". It asks for a username and a password in two labeled text fields, followed by a dark Login button that submits the credentials. No branding, logo or supporting text appears alongside the form, so the page's only visible purpose is collecting account credentials.

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

Source evidenceVirusTotal 14 / 92 · OTX 6 references 8 sources

VirusTotal

14 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
13
Suspicious
1
Undetected
32

Vendor labels

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

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    emily.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    MX
    Value
    alt3.aspmx.l.google.com
    Priority
    10
  • TTL, seconds
    300
    Type
    TXT
    Value
    v=spf1 include:_spf.google.com ~all
  • TTL, seconds
    300
    Type
    MX
    Value
    alt2.aspmx.l.google.com
    Priority
    5
  • TTL, seconds
    300
    Type
    MX
    Value
    alt1.aspmx.l.google.com
    Priority
    5
  • TTL, seconds
    300
    Type
    MX
    Value
    aspmx.l.google.com
    Priority
    1
  • TTL, seconds
    300
    Type
    MX
    Value
    alt4.aspmx.l.google.com
    Priority
    10
  • TTL, seconds
    21600
    Type
    NS
    Value
    jasper.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    emily.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    209.99.189.113
  • TTL, seconds
    300
    Type
    TXT
    Value
    google-site-verification=Ox5tJewWtWVDbDQLa1gpSz1aN3GvlhBTuh36oKALtRE

DNS records observed

JARM fingerprint

2ad2ad0002ad2ad00042d42d00000000f78d2dc0ce6e5bbc5b8149a4872356

Certificate

Subject alternative names
  • *.payutech.pro
  • payutech.pro
Issuer
Let's Encrypt / YR2
Serial
6c11a700efc924851fb36ba54c78425b8de
SHA-256
f90ce77cf4337daf03280c183b1a76d2a069d976ec4079703eff23de35f5a47b
Subject
*.payutech.pro
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID
303
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 13,
    "suspicious": 1,
    "undetected": 32
}
Vendor labels
{
    "ESET": "phishing",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "ADMINUSLabs": "malicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Created
2024-11-23T00:00:00Z
Updated
2024-11-23T00:00:00Z
First seen
2024-11-26T16:03:50Z
DNS records
[
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "emily.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "alt3.aspmx.l.google.com",
        "priority": 10
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=spf1 include:_spf.google.com ~all"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "alt2.aspmx.l.google.com",
        "priority": 5
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "alt1.aspmx.l.google.com",
        "priority": 5
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "aspmx.l.google.com",
        "priority": 1
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "alt4.aspmx.l.google.com",
        "priority": 10
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "jasper.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "emily.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "209.99.189.113"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "google-site-verification=Ox5tJewWtWVDbDQLa1gpSz1aN3GvlhBTuh36oKALtRE"
    }
]
Dns at
2026-11-01T08:28:04Z
Jarm
2ad2ad0002ad2ad00042d42d00000000f78d2dc0ce6e5bbc5b8149a4872356
Certificate
{
    "san": [
        "*.payutech.pro",
        "payutech.pro"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "6c11a700efc924851fb36ba54c78425b8de",
    "sha256": "f90ce77cf4337daf03280c183b1a76d2a069d976ec4079703eff23de35f5a47b",
    "subject": "*.payutech.pro",
    "valid_to": "2027-01-28T23:32:45Z",
    "valid_from": "2026-10-30T23:32:46Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2025-11-24T11:17:55Z",
        "registration": "2024-11-23T17:23:14Z",
        "registrar expiration": "2026-11-23T17:23:14Z",
        "last update of RDAP database": "2026-11-01T08:28:08Z"
    },
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "registrar_iana_id": "303"
}
Separate source record · 13 malicious + 1 suspicious / 92 · 2026-11-01 06:56:05 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-11-01T06:56:05Z
fetched_at
2026-11-02T03:33:12Z
stats
{"timeout":0,"harmless":46,"malicious":13,"suspicious":1,"undetected":32}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

9980b7ff-4122-4c7a-bb8e-945292b9f80d

Final URL

https://payutech.pro/

HTTP response

200

Navigation history

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

DOM structure hash

1fb4da6c6a4c2f6d7fc3bedd320735599584792bbca44114cc92aad0cd53362a

Document hash

7ae65becf9c5e432bbed2966f79cad35b90e13269f0166353627193023a6269a

Phishing classifier result

  • phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    payutech.pro
    Type
    A
    Value
    209.99.189.113

DNSSEC valid

No

IP address

127.0.1.11

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

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing
Original source fields · JSON
Uuid
9980b7ff-4122-4c7a-bb8e-945292b9f80d
Final url
https://payutech.pro/
Status
200
History
[
    {
        "url": "https://payutech.pro/",
        "status": 200
    }
]
DOM structure hash
1fb4da6c6a4c2f6d7fc3bedd320735599584792bbca44114cc92aad0cd53362a
Document hash
7ae65becf9c5e432bbed2966f79cad35b90e13269f0166353627193023a6269a
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "payutech.pro",
        "type": "A",
        "value": "209.99.189.113"
    }
]
Dnssec valid
false
Ip
127.0.1.11

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

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Separate stored summary: Not recorded · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
null
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

Spamhaus DBL

spam domain

URLScan

Malicious · engine verdict · score 92

SHA-256 7ae65becf9c5e432bbed2966f79cad35b90e13269f0166353627193023a6269a

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a19a34-ea48-77ba-9f86-01678ee113a3

Final URL

https://payutech.pro/

HTTP response

200

Redirect type

https-only

Redirects

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

IP address

209.99.189.113

Contacted IP addresses

  • 209.99.189.113

Autonomous systems (ASN)

  • 402253

Server countries

  • CH

Document hash

7ae65becf9c5e432bbed2966f79cad35b90e13269f0166353627193023a6269a

TLS session and certificate

Subject alternative names
  • *.payutech.pro
  • payutech.pro
Cipher
AES_256_GCM
Issuer
YR2
Subject
*.payutech.pro
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

707

Registered domain age, days

707

Certificate age, days

2

Certificate validity, days

89

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
nginx/1.28.2
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a19a34-ea48-77ba-9f86-01678ee113a3
Final url
https://payutech.pro/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://payutech.pro/",
        "from": "http://payutech.pro/",
        "status": 307
    }
]
Ip
209.99.189.113
Contacted IP addresses
[
    "209.99.189.113"
]
Asns
[
    "402253"
]
Countries
[
    "CH"
]
Document hash
7ae65becf9c5e432bbed2966f79cad35b90e13269f0166353627193023a6269a
Tls
{
    "san": [
        "*.payutech.pro",
        "payutech.pro"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "*.payutech.pro",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-28T23:32:45Z",
    "valid_from": "2026-10-30T23:32:46Z"
}
Domain age days
707
Apex age days
707
Tls age days
2
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 92,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx/1.28.2",
    "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
01a19a34-ea48-77ba-9f86-01678ee113a3
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

6 community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-11-02T03:20:09Z

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-11-02T03:20:09Z
source_timestamp
2026-11-02 04:20:09
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
payutech.pro login page with username and password form
ai_description
PhishDestroy describes payutech.pro as a captured login page offering a username and password form with a single Login button.
ai_summary
The captured payutech.pro page presents a single centered login card on a plain light background, headed simply "Login". It asks for a username and a password in two labeled text fields, followed by a dark Login button that submits the credentials. No branding, logo or supporting text appears alongside the form, so the page's only visible purpose is collecting account credentials. The stored VirusTotal domain result reports 14 detections out of 92 engines. ESET reported "phishing"; VIPRE reported "malware".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-02 04:34:07
revision
73c95f7f49efe6e19a9d8aa707a235455a27153e7e44f47af48f4ddc7d0cd4ee
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 23 fields

Mail configuration

MX records
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx.l.google.com
SPF record
v=spf1 include:_spf.google.com ~all
DMARC
Yes
Providers
  • Google Workspace
SPF lookups
1

CAA records

Domain
payutech.pro

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
2
Archived days
7
Snapshots per day
0.01
Average page size, bytes
1292

Crawler rules

User agents
  • *
Present
Yes

Page title and metadata

Page title
Login

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
179
TLS
24
Waiting
235
Connection
68
Download
0
Response time, ms
506

TLS connection

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

Ports

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

Carbon estimate

Bytes
2496
CO₂, grams
0.0001
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    162.159.44.182
    Host
    jasper.ns.cloudflare.com
  • IP address
    172.64.32.155
    Host
    emily.ns.cloudflare.com
DNS zone
payutech.pro

Location

IP address
209.99.189.113
ASN
402253
Organization
SKN Subnet & Telecom Ltd
City
Zurich
Country
CH

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
*.payutech.pro

DNS records

A
  • 209.99.189.113
MX
  • Mail server
    alt4.aspmx.l.google.com
    Priority
    10
  • Mail server
    aspmx.l.google.com
    Priority
    1
  • Mail server
    alt2.aspmx.l.google.com
    Priority
    5
  • Mail server
    alt1.aspmx.l.google.com
    Priority
    5
  • Mail server
    alt3.aspmx.l.google.com
    Priority
    10
NS
  • emily.ns.cloudflare.com
  • jasper.ns.cloudflare.com
SOA
Primary nameserver
emily.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418805972
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
TXT
  • google-site-verification=Ox5tJewWtWVDbDQLa1gpSz1aN3GvlhBTuh36oKALtRE
  • v=spf1 include:_spf.google.com ~all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
209.99.189.113
IP version
4

Redirects

Redirect chain
  • https://payutech.pro

Subdomains

Count
1
Subdomains
  • www.payutech.pro

HTTP headers

Response headers
Server
nginx/1.28.2
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Mail configuration
{
    "mx": [
        "alt3.aspmx.l.google.com",
        "alt4.aspmx.l.google.com",
        "alt1.aspmx.l.google.com",
        "alt2.aspmx.l.google.com",
        "aspmx.l.google.com"
    ],
    "spf": "v=spf1 include:_spf.google.com ~all",
    "dmarc": true,
    "providers": [
        "Google Workspace"
    ],
    "spf_lookups": 1
}
Caa records
{
    "domain": "payutech.pro"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-11-02T03:03:11Z",
    "first": "2025-01-04T06:14:15Z",
    "changes": 2,
    "days_archived": 7,
    "scans_per_day": 0.01,
    "avg_page_bytes": 1292
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "Login"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 179,
        "tls": 24,
        "wait": 235,
        "connect": 68,
        "download": 0
    },
    "response_ms": 506
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        22,
        25,
        80,
        110,
        143,
        443,
        587,
        993,
        995,
        3306,
        8888
    ]
}
Carbon
{
    "bytes": 2496,
    "co2_grams": 0.0001,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.44.182",
            "host": "jasper.ns.cloudflare.com"
        },
        {
            "ip": "172.64.32.155",
            "host": "emily.ns.cloudflare.com"
        }
    ],
    "zone": "payutech.pro"
}
Location
{
    "ip": "209.99.189.113",
    "asn": "402253",
    "org": "SKN Subnet & Telecom Ltd",
    "city": "Zurich",
    "country": "CH"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "*.payutech.pro"
}
DNS records
{
    "A": [
        "209.99.189.113"
    ],
    "MX": [
        "{\"exchange\": \"alt4.aspmx.l.google.com\", \"priority\": 10}",
        "{\"exchange\": \"aspmx.l.google.com\", \"priority\": 1}",
        "{\"exchange\": \"alt2.aspmx.l.google.com\", \"priority\": 5}",
        "{\"exchange\": \"alt1.aspmx.l.google.com\", \"priority\": 5}",
        "{\"exchange\": \"alt3.aspmx.l.google.com\", \"priority\": 10}"
    ],
    "NS": [
        "emily.ns.cloudflare.com",
        "jasper.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"emily.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418805972, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "TXT": [
        "google-site-verification=Ox5tJewWtWVDbDQLa1gpSz1aN3GvlhBTuh36oKALtRE",
        "v=spf1 include:_spf.google.com ~all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "209.99.189.113",
    "family": 4
}
Redirects
{
    "chain": [
        "https://payutech.pro"
    ]
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.payutech.pro"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx/1.28.2",
        "content-type": "text/html; charset=UTF-8"
    }
}

Questions about payutech.pro

Is payutech.pro legit?

PhishDestroy rates payutech.pro as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-02. VirusTotal: 14/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is payutech.pro safe to connect a wallet?

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

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

Checked, no match

Last checked

Stored Capture · 8 captures

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

Domain details

Domain
OTX tags 2026-11all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar PDR IN(IN)
Abuse contactabuse@publicdomainregistry.com, abuse@skntelecom.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for payutech.pro →
Hosting abuse contact abuse@skntelecom.com SKN Subnet & Telecom Ltd · AS402253
RegistrationCreated Nov 23, 2024 — Expires Nov 23, 2026
Registrant countryUnited States VirusTotal WHOIS
Registrant1f8f4166599d23ee29e2c061f3c9524es@ VirusTotal WHOIS
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 2, 2026
DOM Analysisanalyzed Nov 2, 2026score 0/100
Submitted URLhttp://payutech.pro/
Favicon Hash
Observed page title
Login
TLS Certificate
Issued by YR2 · stored validity ends in 87 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Switzerland209.99.189.113
Network ASN
AS402253
Organization
HostRoyale Technologies
Observed location
SwitzerlandZurich, CH
Server header
nginx/1.28.2

Nameservers 2

  • emily.ns.cloudflare.com
  • jasper.ns.cloudflare.com

SOA

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

Mail routing 5 MX records

  • alt3.aspmx.l.google.compriority 10
  • alt2.aspmx.l.google.compriority 5
  • alt1.aspmx.l.google.compriority 5
  • aspmx.l.google.compriority 1
  • alt4.aspmx.l.google.compriority 10

Location describes the IP network.

TLS certificate

Issuer
YR2
Valid from
2026-10-30 23:32:46
Valid until
2027-01-28 23:32:45
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf90ce77cf4337daf03280c183b1a76d2a069d976ec4079703eff23de35f5a47b
Certificate names · 2 SANs
  • *.payutech.pro
  • payutech.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 · 209.99.189.113rapiddns.io
Recorded subdomains1

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

  • www.payutech.proDomain record
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
ADMINUSLabs
alphaMountain.ai
BitDefender
Chong Lua Dao
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
Seclookup
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of payutech.pro · checked Nov 2, 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
1.3 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://payutech.pro/
Final URL: https://payutech.pro/
Login
Response
HTTP 200
HTML body
2.4 KB
Compressed
910 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.28.2
Content-Type: text/html; charset=UTF-8
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 10
Accept-Ranges
bytes
Connection
keep-alive
Content-Encoding
gzip
Content-Length
912
Content-Type
text/html; charset=UTF-8
Date
Mon, 02 Nov 2026 03:03:09 GMT
Etag
"9c0-62b4a10eff700-gzip"
Last-Modified
Thu, 09 Jan 2025 18:22:52 GMT
Server
nginx/1.28.2
Vary
Accept-Encoding

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

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

Captured network requests

Network requests: 2 SHA-256 hashes: 2 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-02 03:06 UTC.

Open this scan on URLScan 01a19a34-ea48-77ba-9f86-01678ee113a3 ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

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

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    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 04:02:52.000000
    Evidence SHA-256
    1316a2d52f529ccc094b3d083a6db7bfdc247877085499acd01d21b98d01eb22
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 04:02:52
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 04:02:52.000000
    Evidence SHA-256
    1316a2d52f529ccc094b3d083a6db7bfdc247877085499acd01d21b98d01eb22
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 04:02:52
    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
    payutech.pro detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • Spamhaus DBL
    Spamhaus DBL recorded: spam domain
  • 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: 14/92
  • OTX Community References
    Community publication references on AlienVault OTX: 6. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

6 entries
  1. AlienVault OTX

    6 community references

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    payutech.pro

    View source
  5. URLScan

    Page captured

    View source
  6. VirusTotal

    14/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

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

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

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

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

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

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

Check for cloaking

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

payutech.pro

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 14 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 6 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.

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