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

swiss-post-ch.com

In short

PhishDestroy stores a record for swiss-post-ch.com. Source observations are dated separately; missing checks do not establish safety.

“Accès refusé”

Review the evidence
Registrar
Gransy, s.r.o
Resolved IP
Luxembourg64.89.161.67Netiface LLC
Registered
Oct 22, 2026
First observed
Oct 29, 2026
PhishDestroy assessment Critical
100/100
Evidence score
First observed Oct 29, 2026 00:38 UTC · PhishDestroy
Risk signals
VirusTotal detections: 3/92 Spamhaus DBL: phishing domain Young domain: 8 days old Google Safe Browsing: threat flag recorded
VirusTotal
3 / 92
engine detections ·
Google Safe Browsing
Flagged
OTX
5
community references
URLScan
Malicious
engine verdict · score 22
Page captures
7
open gallery
Domain age
8 days
registered 2026-10-22 according to WHOIS · source data differ
OTX: 5 refs Oct 29, 2026
X Telegram API

Questions about swiss-post-ch.com

Is swiss-post-ch.com legit?

PhishDestroy stores a record for swiss-post-ch.com. Source observations are dated separately; missing checks do not establish safety.

Is swiss-post-ch.com safe to connect a wallet?

This report does not record which wallet requests swiss-post-ch.com 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 swiss-post-ch.com?

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

Source evidenceVirusTotal 3 / 92 · Google Safe Browsing: flagged · OTX 5 references 7 sources

VirusTotal

3 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
3
Suspicious
0
Undetected
34

Vendor labels

CyRadar
phishing
SOCRadar
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

Gransy, s.r.o.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    64.89.161.67
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.dyna-ns.net
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.swiss-post-ch.com
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.dyna-ns.net

DNS records observed

JARM fingerprint

29d3fd00029d29d00042d43d0000002059a3b916699461c5923779b77cf06b

Certificate

Subject alternative names
  • swiss-post-ch.com
Issuer
Let's Encrypt / YR2
Serial
64c7b61f9df1b33230105790f346e8444ee
SHA-256
9f71e60993855ee4b985fad15e1a55c23c602a2cf3eba40f3054ab2b4519a612
Subject
swiss-post-ch.com
Valid until
Valid from

Registration record

Registrar
Gransy, s.r.o.
Registrar IANA ID
1505
Registrar URL
http://regtons.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client transfer prohibited
  • add period
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 3,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "CyRadar": "phishing",
    "SOCRadar": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
Gransy, s.r.o.
Created
2026-10-22T15:20:49Z
Expires
2027-10-22T15:20:49Z
Updated
2026-10-22T15:21:50Z
First seen
2023-10-07T23:09:02Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "64.89.161.67"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.swiss-post-ch.com",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.dyna-ns.net"
    }
]
Dns at
2026-10-28T12:17:48Z
Jarm
29d3fd00029d29d00042d43d0000002059a3b916699461c5923779b77cf06b
Certificate
{
    "san": [
        "swiss-post-ch.com"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "64c7b61f9df1b33230105790f346e8444ee",
    "sha256": "9f71e60993855ee4b985fad15e1a55c23c602a2cf3eba40f3054ab2b4519a612",
    "subject": "swiss-post-ch.com",
    "valid_to": "2027-01-25T22:38:13Z",
    "valid_from": "2026-10-27T22:38:14Z"
}
Registration record
{
    "registrar": "Gransy, s.r.o.",
    "registrar_iana_id": "1505",
    "registrar_url": "http://regtons.com",
    "created": "2026-10-22T15:20:49Z",
    "updated": "2026-10-22T15:21:50Z",
    "expires": "2027-10-22T15:20:49Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited",
        "add period"
    ],
    "events": {
        "expiration": "2027-10-22T15:20:49Z",
        "last changed": "2026-10-22T15:21:51Z",
        "registration": "2026-10-22T15:20:49Z",
        "registrar expiration": "2027-10-22T15:20:49Z",
        "last update of RDAP database": "2026-10-24T06:31:40Z"
    }
}
Separate source record · 3 malicious + 0 suspicious / 92 · 2026-10-28 12:12:10 UTC

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

record_source
collected_observations.vt
analysis_at
2026-10-28T12:12:10Z
fetched_at
2026-10-29T00:40:03Z
stats
{"timeout":0,"harmless":55,"malicious":3,"suspicious":0,"undetected":34}

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 22

SHA-256 d296a6a59d8a9d143a213793f8da5c763190873bd88e4ae9806267afc02e7d29

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a1851b-1b6a-775c-a142-928559550fad

Final URL

https://swiss-post-ch.com/pages/ban.php

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://swiss-post-ch.com/pages/ban.php
    From
    http://swiss-post-ch.com/pages/ban.php
    Status
    307

IP address

64.89.161.67

Contacted IP addresses

  • 64.89.161.67

Autonomous systems (ASN)

  • 403005

Server countries

  • US

Document hash

02bc7d25a09ecbce2b394ef0277c6c60706c919c5a6851be910a49823d6c9618

Cookies

  • PHPSESSID

TLS session and certificate

Subject alternative names
  • swiss-post-ch.com
Cipher
AES_128_GCM
Issuer
YR2
Subject
swiss-post-ch.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

2245

Differs from the registration date in WHOIS (2026-10-22), which gives 6 days on the scan date 2026-10-29. The two sources disagree; both values are kept as recorded.

Registered domain age, days

2245

Differs from the registration date in WHOIS (2026-10-22), which gives 6 days on the scan date 2026-10-29. The two sources disagree; both values are kept as recorded.

Certificate age, days

1

Certificate validity, days

89

Page requests

3

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=UTF-8
X-powered-by
PHP/8.4.27 PleskLin
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Content-security-policy
default-src 'self'; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self'; media-src 'none'; object-src 'no
X-frame-options
DENY
X-content-type-options
nosniff
Referrer-policy
no-referrer-when-downgrade
Permissions-policy
geolocation=(), microphone=(), camera=(), payment=()
Original source fields · JSON
Uuid
01a1851b-1b6a-775c-a142-928559550fad
Final url
https://swiss-post-ch.com/pages/ban.php
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://swiss-post-ch.com/pages/ban.php",
        "from": "http://swiss-post-ch.com/pages/ban.php",
        "status": 307
    }
]
Ip
64.89.161.67
Contacted IP addresses
[
    "64.89.161.67"
]
Asns
[
    "403005"
]
Countries
[
    "US"
]
Document hash
02bc7d25a09ecbce2b394ef0277c6c60706c919c5a6851be910a49823d6c9618
Cookies
[
    "PHPSESSID"
]
Tls
{
    "san": [
        "swiss-post-ch.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR2",
    "subject": "swiss-post-ch.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-25T22:38:13Z",
    "valid_from": "2026-10-27T22:38:14Z"
}
Domain age days
2245

Differs from the registration date in WHOIS (2026-10-22), which gives 6 days on the scan date 2026-10-29. The two sources disagree; both values are kept as recorded.

Apex age days
2245

Differs from the registration date in WHOIS (2026-10-22), which gives 6 days on the scan date 2026-10-29. The two sources disagree; both values are kept as recorded.

Tls age days
1
Tls valid days
89
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 22,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=UTF-8",
    "x-powered-by": "PHP/8.4.27\nPleskLin",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
    "content-security-policy": "default-src 'self'; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self'; media-src 'none'; object-src 'no",
    "x-frame-options": "DENY",
    "x-content-type-options": "nosniff",
    "referrer-policy": "no-referrer-when-downgrade",
    "permissions-policy": "geolocation=(), microphone=(), camera=(), payment=()"
}
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
01a18359-2cc9-70da-80e5-501fbea2ca45
score
null
malicious
null
result_at
null
enriched_at
2026-10-29T09:14:36Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-29 10:14:36"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

5 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

f9bdeae1-ed49-4af4-92dd-8f49eb0eafe4

Final URL

https://swiss-post-ch.com/pages/ban.php

HTTP response

200

Redirect type

same-domain

Navigation history

  • URL
    https://swiss-post-ch.com/
    Status
    302
  • URL
    https://swiss-post-ch.com/pages/ban.php
    Status
    200

DOM structure hash

3119c719bab2ff24dc2c966ae9cdbe99dff20ce22c3e6318a26f98af9be5a001

Document hash

74e88633d2160f5e90abeaa0b180c3046c5262605ca32f285df59fa221069771

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    swiss-post-ch.com
    Type
    A
    Value
    64.89.161.67

DNSSEC valid

No

IP address

127.0.1.26

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

Registration record

Registrar
Gransy, s.r.o.
Registered
Updated
Expires
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
Original source fields · JSON
Uuid
f9bdeae1-ed49-4af4-92dd-8f49eb0eafe4
Final url
https://swiss-post-ch.com/pages/ban.php
Status
200
Redirected
same-domain
History
[
    {
        "url": "https://swiss-post-ch.com/",
        "status": 302
    },
    {
        "url": "https://swiss-post-ch.com/pages/ban.php",
        "status": 200
    }
]
DOM structure hash
3119c719bab2ff24dc2c966ae9cdbe99dff20ce22c3e6318a26f98af9be5a001
Document hash
74e88633d2160f5e90abeaa0b180c3046c5262605ca32f285df59fa221069771
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "swiss-post-ch.com",
        "type": "A",
        "value": "64.89.161.67"
    }
]
Dnssec valid
false
Ip
127.0.1.26

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

Registration record
{
    "registrar": "Gransy, s.r.o.",
    "created": "2026-10-22T15:20:49Z",
    "updated": "2026-10-22T15:21:50Z",
    "expires": "2027-10-22T15:20:49Z",
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}

PhishDestroy DOM

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

Open report

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

Collected source details

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

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

Mail configuration

SPF lookups
0

CAA records

Domain
swiss-post-ch.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
6
Archived days
9
Snapshots per day
0.02
Average page size, bytes
927

Page title and metadata

Page title
Accès refusé

Trackers

Requests
2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
302
Request timings, ms
DNS
563
TLS
76
Waiting
86
Connection
58
Download
0
Response time, ms
783

TLS connection

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

Ports

Open ports
  • 22
  • 80
  • 443

Carbon estimate

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

DNS servers

Nameservers
  • IP address
    162.159.27.158
    Host
    ns1.dyna-ns.net
  • IP address
    162.159.24.5
    Host
    ns2.dyna-ns.net
DNS zone
swiss-post-ch.com

Cookies

Cookies
  • Name
    PHPSESSID
    Session cookie
    Yes
  • Name
    uid
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    Lax

Location

IP address
64.89.161.67
ASN
36680
Organization
Netiface LLC
City
Schieren
Country
LU

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
swiss-post-ch.com

DNS records

A
  • 64.89.161.67
NS
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
SOA
Primary nameserver
ns1.dyna-ns.net
Hostmaster
hostmaster.swiss-post-ch.com
Serial
2026102203
Refresh, seconds
16384
Retry, seconds
2048
Expiry, seconds
1209600
Minimum TTL, seconds
300

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
DENY
Referrer-Policy
no-referrer-when-downgrade
X-XSS-Protection
1; mode=block
Permissions-Policy
geolocation=(), microphone=(), camera=(), payment=()
X-Content-Type-Options
nosniff
Content-Security-Policy
default-src 'self'; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline'; img-src 'self' data: htt
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
64.89.161.67
IP version
4

Redirects

Redirect chain
  • https://swiss-post-ch.com
  • ../pages/ban.php
Count
1

Page links

Internal links
1

Registration record

Registrar
Gransy, s.r.o.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

HTTP headers

Response headers
Server
nginx
Content-type
text/html; charset=UTF-8
X-powered-by
PHP/8.4.27, PleskLin
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Content-security-policy
default-src 'self'; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self'; media-src 'none'; object-src 'none'; frame-src 'none'; base-uri 'self'; form-action 'self'
X-frame-options
DENY
X-content-type-options
nosniff
Referrer-policy
no-referrer-when-downgrade
Permissions-policy
geolocation=(), microphone=(), camera=(), payment=()
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "swiss-post-ch.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2025-03-23T20:09:21Z",
    "first": "2024-01-04T15:44:39Z",
    "changes": 6,
    "days_archived": 9,
    "scans_per_day": 0.02,
    "avg_page_bytes": 927
}
Page title and metadata
{
    "title": "Accès refusé"
}
Trackers
{
    "requests": 2
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 302,
    "timings": {
        "dns": 563,
        "tls": 76,
        "wait": 86,
        "connect": 58,
        "download": 0
    },
    "response_ms": 783
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 999,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.27.158",
            "host": "ns1.dyna-ns.net"
        },
        {
            "ip": "162.159.24.5",
            "host": "ns2.dyna-ns.net"
        }
    ],
    "zone": "swiss-post-ch.com"
}
Cookies
{
    "cookies": [
        {
            "name": "PHPSESSID",
            "session": true
        },
        {
            "name": "uid",
            "secure": true,
            "http_only": true,
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "64.89.161.67",
    "asn": "36680",
    "org": "Netiface LLC",
    "city": "Schieren",
    "country": "LU"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "swiss-post-ch.com"
}
DNS records
{
    "A": [
        "64.89.161.67"
    ],
    "NS": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.swiss-post-ch.com\", \"serial\": 2026102203, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": "DENY",
    "referrerPolicy": "no-referrer-when-downgrade",
    "xXSSProtection": "1; mode=block",
    "permissionsPolicy": "geolocation=(), microphone=(), camera=(), payment=()",
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": "default-src 'self'; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline'; img-src 'self' data: htt",
    "strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "64.89.161.67",
    "family": 4
}
Redirects
{
    "chain": [
        "https://swiss-post-ch.com",
        "../pages/ban.php"
    ],
    "count": 1
}
Page links
{
    "internal_count": 1
}
Registration record
{
    "registrar": "Gransy, s.r.o.",
    "created": "2026-10-22T15:20:49Z",
    "updated": "2026-10-22T15:21:50Z",
    "expires": "2027-10-22T15:20:49Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html; charset=UTF-8",
        "x-powered-by": "PHP/8.4.27, PleskLin",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
        "content-security-policy": "default-src 'self'; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self'; media-src 'none'; object-src 'none'; frame-src 'none'; base-uri 'self'; form-action 'self'",
        "x-frame-options": "DENY",
        "x-content-type-options": "nosniff",
        "referrer-policy": "no-referrer-when-downgrade",
        "permissions-policy": "geolocation=(), microphone=(), camera=(), payment=()"
    }
}
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 7 captures

Primary capture 1 / 7
SourcePrimary capture
Recorded
StateStored capture
Position1 / 7
Open capture Wayback Download
All capture links and hashes (7)
swiss-post-ch.com: Phishing site — Flagged by Google Safe Browsing, Spamhaus DBL, 3/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card swiss-post-ch.com: Phishing site — Flagged by Google Safe Browsing, Spamhaus DBL, 3/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 86ceb35b147e

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 22 report ↗
Google Safe Browsing Flagged Social engineering checked Oct 30, 2026
IP Reputation Luxembourg64.89.161.67 abuse score 0/100 0 reports checked Oct 29, 2026
Registrar Gransy, s.r.o
Abuse contactabuse@blatant.host, abuse@regtons.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for swiss-post-ch.com →
RegistrationCreated Oct 22, 2026 (8d · Very New!) — Expires Oct 22, 2027
WHOIS statusclientTransferProhibited
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 29, 2026
DOM Analysisanalyzed Oct 29, 2026score 100/100
Submitted URLhttp://swiss-post-ch.com/pages/ban.php
Favicon Hash
Observed page title
Accès refusé
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 87 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Luxembourg64.89.161.67
Network ASN
AS36680
Organization
Netiface LLC
Observed location
LuxembourgSchieren, LU
Server header
nginx

Nameservers 2

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

SOA

  • nsname: ns1.dyna-ns.net
  • hostmaster: hostmaster.swiss-post-ch.com
  • serial: 2026102203
  • refresh: 16384
  • retry: 2048
  • expire: 1209600
  • minttl: 300

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-27 22:38:14
Valid until
2027-01-25 22:38:13
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint9f71e60993855ee4b985fad15e1a55c23c602a2cf3eba40f3054ab2b4519a612
Certificate names · 1 SAN
  • swiss-post-ch.com

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

viewdns.info · 64.89.161.67rapiddns.io

Latest Classified Outcome 2026-10-30 04:03:05 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Probe Inconclusive 20% 2026-10-30 11:06:46 UTC
RDAP registration
Observed timeline last reachable: 2026-10-29 11:07:19 UTC current episode first observed: 2026-10-30 04:03:05 UTC observed RIP window: 2026-10-29 11:07:19 UTC → 2026-10-30 04:03:05 UTC · 16.93h midpoint estimate ≈ 2026-10-29 19:35:12 UTC · precision medium · basis bounded
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.
Recorded subdomains7

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

  • cpanel.swiss-post-ch.comDomain record
  • cpcalendars.swiss-post-ch.comDomain record
  • cpcontacts.swiss-post-ch.comDomain record
  • mail.swiss-post-ch.comDomain record
  • webdisk.swiss-post-ch.comDomain record
  • webmail.swiss-post-ch.comDomain record
  • www.swiss-post-ch.comDomain record
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
CyRadar
SOCRadar

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of swiss-post-ch.com · checked Oct 29, 2026

92
Good
Performance
FCP
2.19 s
First Contentful Paint
LCP
2.19 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
5.57 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://swiss-post-ch.com/pages/ban.php
Final URL: https://swiss-post-ch.com/pages/ban.php
Accès refusé
Response
HTTP 200
HTML body
997 B
Compressed
610 B
Links
1 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/8.4.27
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityContent-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionReferrer-PolicyPermissions-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 18
Cache-Control
no-store, no-cache, must-revalidate, max-age=0
Connection
keep-alive
Content-Encoding
gzip
Content-Length
610
Content-Security-Policy
default-src 'self'; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self'; media-src 'none'; object-src 'none'; frame-src 'none'; base-uri 'self'; form-action 'self'
Content-Type
text/html; charset=UTF-8
Date
Thu, 29 Oct 2026 00:37:33 GMT
Expires
0
Permissions-Policy
geolocation=(), microphone=(), camera=(), payment=()
Pragma
no-cache
Referrer-Policy
no-referrer-when-downgrade
Server
nginx
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Vary
Accept-Encoding
X-Content-Type-Options
nosniff
X-Frame-Options
DENY
X-Powered-By
PHP/8.4.27
X-XSS-Protection
1; mode=block

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

Archived
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
16.93
Estimate basis
Bounded by observations
Estimate precision
Medium

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: 3 SHA-256 hashes: 3 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 01:52 UTC.

Open this scan on URLScan 01a1851b-1b6a-775c-a142-928559550fad ↗

Stored observation history4

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

    dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    redirected

    http_redirect

  3. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  4. Domain monitor · First collection record

    Reachable

All retained availability observations10

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. 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-10-30 12:06:46.000000
    Evidence SHA-256
    3be6d419d5f9d325f8b15c13c40e10510d1ed96c4b8243876e8abb5bfefd5926
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 12:06:46
    Evidence reason
    unavailable
  2. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 05:03:05.462458
    Evidence SHA-256
    f9cff5b9f1950ff481e989dfeecab84b2bf6e847bdeb7bc146f3f704088b4943
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
  3. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 05:03:05.462458
    Evidence SHA-256
    f9cff5b9f1950ff481e989dfeecab84b2bf6e847bdeb7bc146f3f704088b4943
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
  4. current_http_probeunknown
    Observation source
    current_http_probe
    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 00:06:56.000000
    Evidence SHA-256
    984313d2807dea032a5414d8597a61018f9855bf1f89d7474c4700d8d308c7d7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 00:06:56
    Evidence reason
    unavailable
  5. 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-10-30 00:06:56.000000
    Evidence SHA-256
    984313d2807dea032a5414d8597a61018f9855bf1f89d7474c4700d8d308c7d7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 00:06:56
    Evidence reason
    unavailable
  6. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:19.000000
    Evidence SHA-256
    263466ad924aca38e35e49667929853c5a1a25c950df25901bed4c7e72918078
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-29 12:07:19
    Evidence reason
    redirect
  7. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:19.000000
    Evidence SHA-256
    263466ad924aca38e35e49667929853c5a1a25c950df25901bed4c7e72918078
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-29 12:07:19
    Evidence reason
    redirect
  8. 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-29 05:03:05.313035
    Evidence SHA-256
    e8d7330e223cce20a4540e7f3ccd4cc0f3b8c1f41fa08898b82c337408eae933
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 05:03:05.313035
    Evidence reason
  9. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    legacy_alive_unverified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    15
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:43:45.000000
    Evidence SHA-256
    b3622ba9d666826f9da6c1b2547b2067fad9c1e8645f85d0a5c98fecd99e67cb
    Evidence timestamp as recorded
    2026-10-29 01:43:45
  10. http_observationunknown
    Observation source
    http_observation
    Cause
    legacy_alive_unverified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    15
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:43:45.000000
    Evidence SHA-256
    b3622ba9d666826f9da6c1b2547b2067fad9c1e8645f85d0a5c98fecd99e67cb
    Evidence timestamp as recorded
    2026-10-29 01:43:45

Threat Response Pipeline

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

Recorded events: 12. 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
    swiss-post-ch.com detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Google Safe Browsing · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 10 of 10
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 22
  • 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: 3/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • OTX Community References
    Community publication references on AlienVault OTX: 5. 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 Recorded: 1 of 1

Recorded activity

6 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. URLScan

    Page captured

    View source
  3. Wayback Machine

    Page archived

    View source
  4. AlienVault OTX

    5 community references

    View source
  5. Added to PhishDestroy

    swiss-post-ch.com

    View source
  6. VirusTotal

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

swiss-post-ch.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 3 det. ChainPatrol URLQuery Google SB Flagged SSL Labs Stored certificate dates valid CF Radar Open report OTX 5 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 Unverified
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 swiss-post-ch.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/swiss-post-ch.com"
  title="PhishDestroy threat report for swiss-post-ch.com"
  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>