Skip to security report
Analytics Dashboard
Domain security and threat intelligence
crypto007.pro favicon

crypto007.pro

In short

crypto007.pro is a phishing page detected by PhishDestroy on 2026-10-22. Risk: critical (81/100). Registrar: NiceNIC. Status: Last known active. Hosting: CloudFLARENET-EU. PhishDestroy sent 1 abuse report. VirusTotal: 2/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“Сайт в разработке”

Registrar
NiceNIC
Resolved IP
188.114.97.3
Registered
Oct 19, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 2/92 Spamhaus DBL: DBL_SPAM Young domain: 3 days old
Oct 22, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
2 / 92
engine detections
Google Safe Browsing
No threat flag
Page captures
6
open gallery
Domain age
3 days
Reports sent
1
view timeline
Source evidenceVirusTotal 2 / 92 7 sources

VirusTotal

2 / 92 engine detections

Open report

Spamhaus DBL

DBL_SPAM

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Network Security Intelligence Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

Analysis

Critical
VirusTotal
2 / 92
Page captures
6
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy added crypto007.pro to its internal blocklist on 2026-10-22 after an admin report. The site responded with HTTP 200 and showed a Russian‑language “Сайт в разработке” page, which prevented detailed content analysis. The domain was first observed three days after its registration on 2026-10-19.

How the scam works

The presence of a newly registered domain with minimal content is a common characteristic of fraud‑oriented sites such as fake exchanges or credential harvesters, but no specific malicious behavior was observed on this page. The listing therefore reflects a general risk category rather than a confirmed scam mechanism.

Evidence

VirusTotal scanned the domain on 2026-10-22 and reported two detections out of 92 engines, both marked as suspicious (Fortinet labeled it spam, Gridinsoft marked it suspicious). Google Safe Browsing checked the same day and did not flag the site. urlscan.io captured the page on 2026-10-22; its machine‑learning engine gave a malicious score of 73, while the overall verdict was benign. PhishDestroy’s internal blocklist contains the domain, whereas external blocklists checked on the same date reported zero hits, and OTX listed no pulses.

Infrastructure

The domain was registered on 2026-10-19 through NICENIC INTERNATIONAL GROUP CO., LIMITED. Hosting is provided via Cloudflare, with recorded IP addresses in the 188.114.97.0/24 range and an IPv6 address in the 2a06:98c1:3120::/64 block. A Let's Encrypt TLS certificate covering *.crypto007.pro was issued on 2026-10-19 and is valid until 2027-01-17; DNSSEC is not enabled.

What to do

Simply visiting the page does not indicate compromise, but avoid entering credentials, wallet addresses, or private keys. If any sensitive information was submitted, change associated passwords and monitor relevant accounts for unauthorized activity. Defenders should add crypto007.pro to blocklists, monitor DNS queries for the recorded IPs, and review logs for any connections to this domain.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-22T12:56:03Z)VirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-10-22T12:54:50Z

Observed: · Retrieved:

Uuid
01a163ad-8caf-71f2-8ef9-2b78ba423809
Final url
https://crypto007.pro/
Status
200
Ip
188.114.97.3
Contacted IP addresses
[
    "188.114.97.3"
]
Asns
[
    "13335"
]
Document hash
6ffdab79521871f6977d6cd357c485a2636920608e75312af9326f62348f180c
Script hashes
[
    "833567d505fed696beed49ecf5ff70ea1f2b838f0c8f64c1b8d2b5564a68e343",
    "2c752a401191671d5bbbe7514f5828bbb0a7cc50bfbe77ddaf1b1ccba4412ed2",
    "6fae740f3b027bbe7ef3763f726c42e8b2232e55889caae96c7354b30646e352",
    "53685a01264114d894a9029fa5db30ffad50793404b1ce72b28daf944aaecbc9"
]
Globals
[
    "__next_f",
    "webpackChunk_N_E",
    "next",
    "_N_E_STYLE_LOAD"
]
Tls
{
    "san": [
        "*.crypto007.pro",
        "crypto007.pro"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "crypto007.pro",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-17T16:51:02Z",
    "valid_from": "2026-10-19T16:51:03Z"
}
Domain age days
2
Apex age days
2
Tls age days
2
Tls valid days
89
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 73,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains; preload",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin"
}
Cloudflare Radar · 2026-10-22T12:56:03Z

Observed: · Retrieved:

Uuid
f76ccda6-7d26-442d-a963-111044664288
Final url
https://crypto007.pro/
Status
200
History
[
    {
        "url": "https://crypto007.pro/",
        "status": 200
    }
]
DOM structure hash
7bd7da27f1912b81309df72d826445430e7280432e124cc5af725f74d6753992
Document hash
44b70b41d0c2b5b387f7433bfffeb1b45eee99ff26fd03eda28e29e0d8cd8933
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "crypto007.pro",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "crypto007.pro",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "crypto007.pro",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    },
    {
        "name": "crypto007.pro",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    }
]
Dnssec valid
false
Ip
188.114.96.0
VirusTotal · 2026-10-22T03:59:11Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 0,
    "suspicious": 2,
    "undetected": 37
}
Vendor labels
{
    "Fortinet": "spam",
    "Gridinsoft": "suspicious"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "Forcepoint ThreatSeeker": "newly registered websites"
}
First seen
2026-10-19T18:08:44Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.38.190"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "arch.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::ac43:89c7"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.137.199"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "arch.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "heidi.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3030::6815:26be"
    }
]
Dns at
2026-10-22T04:32:42Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.crypto007.pro",
        "crypto007.pro"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "600a5a796077ee5f0efde2bd103091d7348",
    "sha256": "194d1316a25445594c718822dbc101be0f289ac82c999ee210774d1af99e74a0",
    "subject": "crypto007.pro",
    "valid_to": "2027-01-17T16:51:02Z",
    "valid_from": "2026-10-19T16:51:03Z"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-18T16:00:00Z",
        "registration": "2026-10-18T16:00:00Z",
        "registrar expiration": "2027-10-18T16:00:00Z",
        "last update of RDAP database": "2026-10-18T16:00:00Z"
    },
    "registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
    "registrar_iana_id": "3765"
}
Website checks · 2026-10-22T12:57:04Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "crypto007.pro"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Page title and metadata
{
    "title": "Сайт в разработке",
    "description": "Crypto exchange"
}
Trackers
{
    "requests": 6
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 7,
        "tls": 35,
        "wait": 141,
        "connect": 24,
        "download": 35
    },
    "response_ms": 242
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 6315,
    "co2_grams": 0.0002,
    "cleaner_than": 82
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.33.68",
            "host": "arch.ns.cloudflare.com"
        },
        {
            "ip": "162.159.38.236",
            "host": "heidi.ns.cloudflare.com"
        }
    ],
    "zone": "crypto007.pro"
}
Location
{
    "ip": "2a06:98c1:3121::9",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "crypto007.pro"
}
DNS records
{
    "A": [
        "188.114.96.9",
        "188.114.97.9"
    ],
    "NS": [
        "arch.ns.cloudflare.com",
        "heidi.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"arch.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2417946146, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2a06:98c1:3120::9",
        "2a06:98c1:3121::9"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": "SAMEORIGIN",
    "referrerPolicy": "strict-origin-when-cross-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3120::9",
    "family": 6
}
Redirects
{
    "chain": [
        "https://crypto007.pro"
    ]
}
Tech stack
{
    "technologies": [
        "Node.js",
        "React",
        "Next.js",
        "Priority Hints",
        "HSTS",
        "Cloudflare",
        "Webpack",
        "Module Federation",
        "HTTP/3"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31536000; includeSubDomains; preload",
        "x-frame-options": "SAMEORIGIN",
        "x-content-type-options": "nosniff",
        "referrer-policy": "strict-origin-when-cross-origin"
    }
}

Questions about crypto007.pro

Is crypto007.pro legit?

No. PhishDestroy classifies crypto007.pro as a phishing page (risk: critical, 81/100); it was first detected on 2026-10-22. VirusTotal: 2/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is crypto007.pro safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on crypto007.pro. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used crypto007.pro?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 6 captures

Primary capture 1 / 6
SourcePrimary capture
Recorded2026-10-22 12:55 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://crypto007.pro/
Position1 / 6
Open capture Wayback Download

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar NiceNIC RU(RU) PhishDestroy Investigation
Abuse contactabuse@nicenic.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for crypto007.pro →
RegistrationCreated Oct 19, 2026 (3d · Brand New!) — Expires Oct 19, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 22, 2026score 81/100
Submitted URLhttps://crypto007.pro/
Favicon Hash
Case ID
Observed page title
Сайт в разработке
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 87 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
London, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • arch.ns.cloudflare.com
  • heidi.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-19 16:51:03
Valid until
2027-01-17 16:51:02
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint194d1316a25445594c718822dbc101be0f289ac82c999ee210774d1af99e74a0
Certificate names · 2 SANs
  • *.crypto007.pro
  • crypto007.pro

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

viewdns.info · 188.114.97.3rapiddns.io
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed
Fortinet
Gridinsoft
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of crypto007.pro · checked Oct 22, 2026

100
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
0.78s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
24ms
Total Blocking Time
SI
1.49s
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: https://crypto007.pro/
Сайт в разработке
Crypto exchange
Response
HTTP 200
HTML body
6.2 KB
Compressed
2.2 KB
Links
0 internal · 0 external
Detected technologies
reactcloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Server: cloudflare
Security headers present
Strict-Transport-SecurityX-Frame-OptionsX-Content-Type-OptionsReferrer-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 20
alt-svc
h3=":443"; ma=86400
Cache-Control
private, no-cache, no-store, max-age=0, must-revalidate
cf-cache-status
DYNAMIC
CF-RAY
a4e8a98cdb2cd2b6-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Thu, 22 Oct 2026 12:56:29 GMT
Link
; rel=preload; as="style"
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Referrer-Policy
strict-origin-when-cross-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=xWwcTAq7Wg%2F9dS53OWlNiqszbXcs8dU7EejyDZqCfCwCTmyTqnF%2B4Pekzie9F%2FNdJpIwmN%2BcG3OIL2MFdW6HfbL67fqxOQjZPxr%2Fz0F%2F8r2yMuclubQz6lJRFUEYXadZ"}]
Server
cloudflare
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Transfer-Encoding
chunked
Vary
rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding
Via
1.1 Caddy
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
x-tenant-host
crypto007.pro

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

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

Stored observation history1

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

  1. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. Abuse report sent

    PD-20261022-183DD3

    abuse@identitydigital.com
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    2/92 engine detections

    View source
  4. Added to PhishDestroy

    crypto007.pro

    View source
  5. URLScan

    Page captured

    View source

Check for cloaking

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

crypto007.pro

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 2 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261022-183DD3 Recipient: abuse@identitydigital.com
PDF notice generated
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?

5 evidence signal groups linked 1 stored notification records Last known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 crypto007.pro)
  • Communications — emails, texts, phone numbers, usernames the scammer used

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

Where should I report the scam?

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

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

How do phishing scams typically work?

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

How can I protect myself in the future?

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

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

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

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

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

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

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

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/crypto007.pro"
  title="PhishDestroy threat report for crypto007.pro"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>