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

trezrr-iio-start.webflow.io

In short

PhishDestroy first recorded trezrr-iio-start.webflow.io on 2026-09-13. VirusTotal: 4/92 engines flag it.

Review the evidence
Registrar
United StatesWebflow
Resolved IP
Canada172.64.151.8Cloudflare, Inc. · CDN
Registered
May 8, 2013
First observed
Sep 13, 2026
PhishDestroy assessment High
65/100
Evidence score
Availability Content unavailable Content was unavailable in the latest observation Observed HTTP probe
Risk signals
VirusTotal detections: 4/92
VirusTotal
4 / 92
engine detections ·
Page captures
1
open gallery
Domain age
4,926 days
registered 2013-05-08 according to RDAP
Sep 13, 2026 CDN
X Telegram API

Questions about trezrr-iio-start.webflow.io

Is trezrr-iio-start.webflow.io legit?

PhishDestroy rates trezrr-iio-start.webflow.io as high risk (65/100) from the recorded evidence; it was first recorded on 2026-09-13. VirusTotal: 4/92 engines flag it. Treat the site as unsafe.

Is trezrr-iio-start.webflow.io safe to connect a wallet?

This report does not record which wallet requests trezrr-iio-start.webflow.io 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 trezrr-iio-start.webflow.io?

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 4 / 92 5 sources

VirusTotal

4 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
4
Suspicious
0
Undetected
35

Vendor labels

Fortinet
phishing
PhishFort
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
malicious

Reputation score

0

Tags

  • dga

Categories

alphaMountain.ai
Hosting, Phishing (alphaMountain.ai)

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    104.18.36.248
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2a06:98c1:3102::ac40:9708
  • TTL, seconds
    300
    Type
    A
    Value
    172.64.151.8
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2a06:98c1:3105::6812:24f8

DNS records observed

JARM fingerprint

27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

Subject alternative names
  • webflow.io
  • *.webflow.io
Issuer
Google Trust Services / WE1
Serial
ac972ef95a18ab8f0e5a2917e958d6da
SHA-256
5302eb12d2c1ddc8020e4565aef253a59e28b4a9aede60f73e4fe6cb516fd2a7
Subject
webflow.io
Valid until
Valid from

Registration record

Registrar
MarkMonitor Inc.
Registrar IANA ID
292
Registrar URL
http://www.markmonitor.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • journey.ns.cloudflare.com
  • lamar.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 4,
    "suspicious": 0,
    "undetected": 35
}
Vendor labels
{
    "Fortinet": "phishing",
    "PhishFort": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "malicious"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Hosting, Phishing (alphaMountain.ai)"
}
Registrar
MarkMonitor Inc.
Created
2013-05-08T02:20:57Z
Expires
2028-05-08T02:20:57Z
Updated
2026-08-12T04:04:30Z
First seen
2026-09-13T12:18:46Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "104.18.36.248"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a06:98c1:3102::ac40:9708"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.64.151.8"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a06:98c1:3105::6812:24f8"
    }
]
Dns at
2026-10-16T00:27:00Z
Jarm
27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "webflow.io",
        "*.webflow.io"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "ac972ef95a18ab8f0e5a2917e958d6da",
    "sha256": "5302eb12d2c1ddc8020e4565aef253a59e28b4a9aede60f73e4fe6cb516fd2a7",
    "subject": "webflow.io",
    "valid_to": "2026-12-21T03:46:57Z",
    "valid_from": "2026-09-22T02:47:08Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2013-05-08T02:20:57Z",
    "updated": "2025-02-25T20:53:31Z",
    "expires": "2028-05-08T02:20:57Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "journey.ns.cloudflare.com",
        "lamar.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 4 malicious + 0 suspicious / 92 · 2026-10-16 00:26:32 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-16T00:26:32Z
fetched_at
2026-10-22T01:54:10Z
stats
{"timeout":0,"harmless":53,"malicious":4,"suspicious":0,"undetected":35}

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

a76e128f-325f-44a7-84ae-c8deecb55963

Final URL

https://trezrr-iio-start.webflow.io/

HTTP response

404

Navigation history

  • URL
    https://trezrr-iio-start.webflow.io/
    Status
    404

DOM structure hash

4932075438459d054af6b75a0d6585b123ae775f36579c095159b2af33360488

Document hash

90c032f35272ba1a7aa93027ab635e6610d4f24cf9e53c0624d00f065d7c7e7d

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    trezrr-iio-start.webflow.io
    Type
    A
    Value
    172.64.151.8
  • Name
    trezrr-iio-start.webflow.io
    Type
    A
    Value
    104.18.36.248
  • Name
    trezrr-iio-start.webflow.io
    Type
    AAAA
    Value
    2a06:98c1:3105::6812:24f8
  • Name
    trezrr-iio-start.webflow.io
    Type
    AAAA
    Value
    2a06:98c1:3102::ac40:9708

DNSSEC valid

No

IP address

172.64.151.8

Registration record

Registrar
MarkMonitor Inc.
Registered
Updated
Expires
Nameservers
  • lamar.ns.cloudflare.com
  • journey.ns.cloudflare.com
Original source fields · JSON
Uuid
a76e128f-325f-44a7-84ae-c8deecb55963
Final url
https://trezrr-iio-start.webflow.io/
Status
404
History
[
    {
        "url": "https://trezrr-iio-start.webflow.io/",
        "status": 404
    }
]
DOM structure hash
4932075438459d054af6b75a0d6585b123ae775f36579c095159b2af33360488
Document hash
90c032f35272ba1a7aa93027ab635e6610d4f24cf9e53c0624d00f065d7c7e7d
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "trezrr-iio-start.webflow.io",
        "type": "A",
        "value": "172.64.151.8"
    },
    {
        "name": "trezrr-iio-start.webflow.io",
        "type": "A",
        "value": "104.18.36.248"
    },
    {
        "name": "trezrr-iio-start.webflow.io",
        "type": "AAAA",
        "value": "2a06:98c1:3105::6812:24f8"
    },
    {
        "name": "trezrr-iio-start.webflow.io",
        "type": "AAAA",
        "value": "2a06:98c1:3102::ac40:9708"
    }
]
Dnssec valid
false
Ip
172.64.151.8
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2013-05-08T02:20:57Z",
    "updated": "2026-08-12T04:04:30Z",
    "expires": "2028-05-08T02:20:57Z",
    "nameservers": [
        "lamar.ns.cloudflare.com",
        "journey.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

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

Collected source details

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

Every stored field, with its source and date
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 1 capture

Cloudflare Radar 1 / 1
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status404
Final URLhttps://trezrr-iio-start.webflow.io/
Position1 / 1
Open capture Source Report Wayback Download
All capture links and hashes (1)
  • Cloudflare Radar · 2026-09-21 07:43 UTC · Source report
    SHA-256: a380e448eb3101674f4c67f891f37ba29b76e79d0bcca3163d4b1510d947431b · 22886 bytes
trezrr-iio-start.webflow.io: caution — 3/89 VirusTotal engines. PhishDestroy risk score 65/100 (high).
Social preview card trezrr-iio-start.webflow.io: caution — 3/89 VirusTotal engines. PhishDestroy risk score 65/100 (high). v 4c2df9cc06e4

Domain details

Domain
IP Context Canada172.64.151.8 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Webflow US(US)
Abuse contact["abusecomplaints@markmonitor.com", "53d8147c627f0cces@webflow.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for webflow.io →
Registration (base domain)webflow.io · Created May 8, 2013 — Expires May 8, 2028
HTTP Status404 Not Found
Time to First Unavailability 7 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 13, 2026
Observed page title
404 - Page not found
Automated brand references
Google
TLS Certificate
Issued by Google Trust Services / WE1

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.64.151.8
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • journey.ns.cloudflare.com
  • lamar.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-07-25 02:21:21
Valid until
2026-10-23 03:21:05
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-09-20 19:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta4ffdefa8d99689893e2aafdf9588b6f8f2f8ec47698ea534dbfa409dbbde19d
Certificate names · 1 SAN
  • webflow.io

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

viewdns.info · 172.64.151.8rapiddns.io

Latest Classified Outcome 2026-11-01 02:14:55 UTC

No phishing content was served at the latest check.

Technical details
Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Stale Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-11-01 02:14:55 UTC
RDAP registration
Observed timeline last reachable: 2026-09-13 17:28:09 UTC current episode first observed: 2026-10-01 01:53:37 UTC observed RIP window: 2026-09-13 17:28:09 UTC → 2026-10-01 01:53:37 UTC · 416.42h midpoint estimate ≈ 2026-09-22 09:40:53 UTC · precision low · 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.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 3 detections
alphaMountain.ai
Fortinet
PhishFort
Registration & observation details8

Availability observations

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

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

Stored observation history16

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

    inactive

    http_no_content

  2. Availability monitor · Recorded state

    inactive

    http_no_content

  3. Availability monitor · Recorded state

    inactive

    http_no_content

  4. Availability monitor · Recorded state

    inactive

    http_no_content

  5. Availability monitor · Recorded state

    inactive

    http_no_content

Earlier observations 11
  1. Availability monitor · Recorded state

    inactive

    http_no_content

  2. Availability monitor · Recorded state

    inactive

    http_no_content

  3. Availability monitor · Recorded state

    inactive

    http_no_content

  4. Availability monitor · Recorded state

    inactive

    http_no_content

  5. Availability monitor · Recorded state

    inactive

    http_no_content

  6. Availability monitor · Recorded state

    inactive

    http_no_content

  7. Availability monitor · Recorded state

    inactive

    http_no_content

  8. Availability monitor · Recorded state

    inactive

    http_no_content

  9. Availability monitor · Recorded state

    inactive

    http_no_content

  10. Domain monitor · Recorded state

    Reachable→Unavailable

  11. Domain monitor · First collection record

    Reachable

Separate monitor HTTP observation

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

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-09-13 19:28:09
All retained availability observations32

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

  1. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:14:55.000000
    Evidence SHA-256
    c60027794e38f2265dfef7e95f72773e4248fc8c4cdb8ed259f2588f8c8a37ed
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-11-01 03:14:55
    Evidence reason
    http_other
  2. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:14:55.000000
    Evidence SHA-256
    c60027794e38f2265dfef7e95f72773e4248fc8c4cdb8ed259f2588f8c8a37ed
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-11-01 03:14:55
    Evidence reason
    http_other
  3. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:16:05.000000
    Evidence SHA-256
    794c16d10205e19fe9977e57b69d0014bf32259be1595af5d4d6bd31ef7031e9
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-31 03:16:05
    Evidence reason
    http_other
  4. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:16:05.000000
    Evidence SHA-256
    794c16d10205e19fe9977e57b69d0014bf32259be1595af5d4d6bd31ef7031e9
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-31 03:16:05
    Evidence reason
    http_other
  5. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:24:50.000000
    Evidence SHA-256
    6b1c4693ed1981ec671c5dc03a7dd02cce99c6cf3c035104380235ed04a99130
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 03:24:50
    Evidence reason
    http_other
  6. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:24:50.000000
    Evidence SHA-256
    c80530374715f21462543f8ca9264e0ef6ff1db1573e366dd0a02a45bfbb2085
    Evidence timestamp as recorded
    2026-10-29 03:24:50
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  7. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 03:25:38.000000
    Evidence SHA-256
    09113919a0f641220d200a4937024f6eaa2203cc2fffb48c90717d7356360d19
    Evidence timestamp as recorded
    2026-10-27 03:25:38
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  8. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 03:25:38.000000
    Evidence SHA-256
    40b5efdd0d017dbd7c39c023be11d8ce4230b1777d0e52f894594f3ad64a4ecc
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-27 03:25:38
    Evidence reason
    http_other
  9. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:21:46.000000
    Evidence SHA-256
    04909738075f6e8e2abcdc12e79960c8d68c9d7e1315af1d37863610e29f92f9
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 03:21:46
    Evidence reason
    http_other
  10. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:21:46.000000
    Evidence SHA-256
    15d1828feba9638273fd07d8b71ca7e4390b34d91af8c8107db7255030a645d4
    Evidence timestamp as recorded
    2026-10-25 03:21:46
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  11. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 03:26:18.000000
    Evidence SHA-256
    0e3434e5dc548c09e5bb1080be7f11c10d74a595521cb6e08e3665b6cd4e43f2
    Evidence timestamp as recorded
    2026-10-23 03:26:18
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  12. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 03:26:18.000000
    Evidence SHA-256
    e28e0c0564aa158077873ff1cb23f18e17466b89688e35cabd6b8ea77e7160a2
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-23 03:26:18
    Evidence reason
    http_other
  13. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 03:16:13.000000
    Evidence SHA-256
    3fd5c51130bb3e29f57ca9bf8e35e8d8df792de0717b62c83fd79ba5adf58313
    Evidence timestamp as recorded
    2026-10-21 03:16:13
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  14. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 03:16:13.000000
    Evidence SHA-256
    fe2edf0fd5a8c3ac337fa9e39d647cf24feaaa8f69ffd96a06497a66b3fd2c17
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-21 03:16:13
    Evidence reason
    http_other
  15. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 03:15:57.000000
    Evidence SHA-256
    7787554c3ece32162723cd6e5020b5c12e3caaaa14cd6b5f1471dd6daedbb476
    Evidence timestamp as recorded
    2026-10-19 03:15:57
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  16. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 03:15:57.000000
    Evidence SHA-256
    9ada919733beb93d2b537793e8da773053936a6a6a9a311adaaac937f476dbac
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-19 03:15:57
    Evidence reason
    http_other
  17. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-17 03:15:21.000000
    Evidence SHA-256
    57d283cd0931778e406ed2827751b35367be9c2ad92d0465777b85cb36d1a820
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-17 03:15:21
    Evidence reason
    http_other
  18. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-17 03:15:21.000000
    Evidence SHA-256
    7058a813efa297c580ee7e2a37f4c0d95146028ea7453c02c2be38f7b9b818ca
    Evidence timestamp as recorded
    2026-10-17 03:15:21
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  19. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-15 03:16:13.000000
    Evidence SHA-256
    4128e84bde8fabc8fe5c23dd22761f816726e118916eb7c546ba310180b0631a
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-15 03:16:13
    Evidence reason
    http_other
  20. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-15 03:16:13.000000
    Evidence SHA-256
    76947513d90b79fd9cb8eb7d30c195d4719551aaf680cdd6755d3bf955d27baf
    Evidence timestamp as recorded
    2026-10-15 03:16:13
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  21. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-13 03:30:48.000000
    Evidence SHA-256
    a1ab31705423d09c872220d5f64b2e87e0ef9e4c496db6fb394b068e01070107
    Evidence timestamp as recorded
    2026-10-13 03:30:48
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  22. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-13 03:30:48.000000
    Evidence SHA-256
    f9c736aa0ef4fa7862809d90d3656535c9d6ae1ce7ce647326f383dc36e5dafa
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-13 03:30:48
    Evidence reason
    http_other
  23. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-11 03:30:05.000000
    Evidence SHA-256
    4c03508d5571db3f0b11bab4c4d189d9db9690792c77931f9ea21fdcba0c1417
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-11 03:30:05
    Evidence reason
    http_other
  24. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-11 03:30:05.000000
    Evidence SHA-256
    a731b532fdc8e33d4031f0d4a953007b7c6e34684abb8af4f4da1689384d0400
    Evidence timestamp as recorded
    2026-10-11 03:30:05
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  25. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-09 03:43:12.000000
    Evidence SHA-256
    174a9ac8fc914b6d045ed3aa0dd753638049508a6ed1db8758d66ee586f74ee0
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-09 03:43:12
    Evidence reason
    http_other
  26. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-09 03:43:12.000000
    Evidence SHA-256
    d048b863a5cb63e75ef96846e0bb13b9871773ef14b600307bd7a77a93316f7c
    Evidence timestamp as recorded
    2026-10-09 03:43:12
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  27. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-07 04:06:40.000000
    Evidence SHA-256
    1bfd7803cfec67a729fe9658977ff29908d2860a568a8d06956b38891f9c4c85
    Evidence timestamp as recorded
    2026-10-07 04:06:40
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  28. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-07 04:06:40.000000
    Evidence SHA-256
    4da8c9eef4f24503993b6cfc77e93097a96b35abf33ac14473091bec0c173fc2
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-07 04:06:40
    Evidence reason
    dead_http
  29. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-03 03:51:30.000000
    Evidence SHA-256
    3fec1183fb83d3a17097354b03d2c0fa8c1f8a82dda601b59c9ae073ffe7b5d3
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-03 03:51:30
    Evidence reason
    dead_http
  30. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-03 03:51:30.000000
    Evidence SHA-256
    7c0e95414944803d1b6f6575d705bfee7a703d043a9ce472f962e5771e60737f
    Evidence timestamp as recorded
    2026-10-03 03:51:30
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  31. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-01 03:53:37.000000
    Evidence SHA-256
    289d742c8107bae0ba698f30fc36afe8141601f4626995af1d764f7990c37ff8
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-01 03:53:37
    Evidence reason
    dead_http
  32. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-01 03:53:37.000000
    Evidence SHA-256
    d8b83ce7129d0bc7ace7e528bc45b8db4f31784f45990fb70cd481eac448b579
    Evidence timestamp as recorded
    2026-10-01 03:53:37
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 10. 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
    trezrr-iio-start.webflow.io detected and queued for full analysis
Threat Intelligence ChecksCloudflare Radar Report · VirusTotal · Automated brand label: Google · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable Recorded: 6 of 6
  • 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.
  • VirusTotal
    Detections recorded on VirusTotal: 4/92
  • Automated brand label: Google
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • Content Observed Unavailable
    Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Publication & AvailabilityDestroyList Published · Content Observed Unavailable · Time to First Unavailability Recorded: 3 of 3
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Content Observed Unavailable
    The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 173

Recorded activity

2 entries
  1. VirusTotal

    4/92 engine detections

    View source
  2. Added to PhishDestroy

    trezrr-iio-start.webflow.io

    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

Community intelligence

1 community report

CategoryImpersonation

Brand abuse: impersonation, fake affiliation, impersonating Trezor

Check for cloaking

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

trezrr-iio-start.webflow.io

Evidence & External Reports

Security Analysis
VirusTotal 4 det. ChainPatrol ChainAbuse 1 report URLQuery SSL Labs Certificate hostname mismatch CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Third-Party Detection — ChainAbuse
1 report filed for trezrr-iio-start.webflow.io · category: Impersonation · source checked
Flagged by automated brand-abuse detection · Sep 13, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
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?

2 evidence signal groups linked Content unavailable
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 trezrr-iio-start.webflow.io)
  • 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/trezrr-iio-start.webflow.io"
  title="PhishDestroy threat report for trezrr-iio-start.webflow.io"
  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>