Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 17. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
bitpro-pulse.com favicon

bitpro-pulse.com

In short

bitpro-pulse.com is a phishing page detected by PhishDestroy on 2026-10-23.

“Bitpro Pulse ™ | The Official & Updated Website 2025 🥇”

Review the evidence
Registrar
Internet Domain Servic…
Resolved IP
185.98.60.138
Registered
Oct 16, 2024
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 17/92 Scam type: Impersonation
VirusTotal
17 / 92
engine detections ·
OTX
5
community references
Cloudflare Radar
Phishing
Page captures
5
open gallery
Domain age
739 days
Reports sent
1
view timeline
OTX: 5 refs Oct 23, 2026 1 Report Sent
X Telegram API
ABUSE NOTICE · 24H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@internet.bs. The latest stored availability evidence still shows the domain reachable; 2 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
2 days
Reports sent
1
Latest case ID
PD-20261023-C5F6C2
Current status
HTTP 200 at latest stored check

Analysis

Domain summary

bitpro-pulse.com is a phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (100/100). Registrar: Internet Domain Servic…. Status: Last known active. Hosting: Ideal Hosting Teknoloji A.S. PhishDestroy sent 1 abuse report. VirusTotal: 17/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
17 / 92
OTX
5 community refs
Page captures
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy’s automated assessment classified bitpro-pulse.com as an impersonation phishing page. The recorded page title was “Bitpro Pulse ™ | The Official & Updated Website 2025 🥇”, and the domain was first observed by PhishDestroy on 2026-10-23 with an HTTP 200 response.

How the scam works

Impersonation phishing pages copy the branding and visual design of legitimate cryptocurrency services to lure visitors into entering login credentials, private keys, or approving wallet transactions. Victims who provide such information may have their accounts compromised or funds drained.

Evidence

VirusTotal reported 14 malicious and 3 suspicious detections from 92 engines on 2026-10-23, including vendors such as BitDefender, ESET and Kaspersky. Google Safe Browsing showed no flag on the same date. Cloudflare Radar flagged the domain as malicious malware on 2026-10-23. URLScan captured two scans: a clean verdict on 2026-07-30 and a malicious machine‑learning score of 97 on 2026-10-23. PhishDestroy’s internal blocklist marks the domain, and OTX lists five pulses referencing it.

Infrastructure

The domain was registered on 2024-10-16 through Internet Domain Service BS Corp., used the nameservers ns1.cryptodns.co and ns2.cryptodns.co, resolved to the IP 185.98.60.138 that was associated with Ideal Hosting Teknoloji A.S. in Turkey, and presented a Let’s Encrypt certificate valid from 2026-09-18 to 2026-12-17.

What to do

Visitors should avoid entering any cryptocurrency credentials or approving wallet actions on this site; if they have already done so, they should change passwords and monitor accounts for unauthorized activity. Defenders can block the domain in firewalls or proxies, monitor DNS queries for the recorded name, and apply the listed indicators to security tooling.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-23T08:32:23Z)URLQuery screenshotURLScan screenshot (2026-07-30T07:47:30Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 17 / 92 · OTX 5 references 9 sources

VirusTotal

17 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
44
Malicious
14
Suspicious
3
Undetected
31

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
malware
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Emsisoft
malware
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Dr.Web
not recommended site
Google
financial_services
Sophos
phishing and fraud
alphaMountain.ai
Phishing (alphaMountain.ai)

Created

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.cryptodns.co
  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.cryptodns.co
  • TTL, seconds
    300
    Type
    A
    Value
    185.98.60.138
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    admin.cryptodns.co
    Value
    ns1.cryptodns.co

DNS records observed

JARM fingerprint

1dd40d40d00040d00042d43d000000831b6af40378e2dd35eeac4e9311926e

Certificate

Subject alternative names
  • *.bitpro-pulse.com
  • bitpro-pulse.com
Issuer
Let's Encrypt / YE1
Serial
53517fe94372170d22595156f7a891f6d2a
SHA-256
1fea0f50d5690e796dc72cd059f2bcb914cac589709791e760b10df04e9e6280
Subject
bitpro-pulse.com
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
Internet Domain Service BS Corp.
Registrar IANA ID
2487
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 14,
    "suspicious": 3,
    "undetected": 31
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Emsisoft": "malware",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Dr.Web": "not recommended site",
    "Google": "financial_services",
    "Sophos": "phishing and fraud",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Created
2024-10-16T00:00:00Z
Updated
2026-03-04T00:00:00Z
First seen
2024-10-16T09:57:28Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.cryptodns.co"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.cryptodns.co"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "185.98.60.138"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "admin.cryptodns.co",
        "value": "ns1.cryptodns.co"
    }
]
Dns at
2026-10-18T23:24:02Z
Jarm
1dd40d40d00040d00042d43d000000831b6af40378e2dd35eeac4e9311926e
Certificate
{
    "san": [
        "*.bitpro-pulse.com",
        "bitpro-pulse.com"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "53517fe94372170d22595156f7a891f6d2a",
    "sha256": "1fea0f50d5690e796dc72cd059f2bcb914cac589709791e760b10df04e9e6280",
    "subject": "bitpro-pulse.com",
    "valid_to": "2026-12-17T16:37:10Z",
    "valid_from": "2026-09-18T16:37:11Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-16T09:31:37Z",
        "last changed": "2026-05-20T13:59:09Z",
        "registration": "2024-10-16T09:31:37Z",
        "registrar expiration": "2027-10-16T09:31:37Z",
        "last update of RDAP database": "2026-10-18T11:56:05Z"
    },
    "registrar": "Internet Domain Service BS Corp.",
    "registrar_iana_id": "2487"
}
Separate source record · 14 malicious + 3 suspicious / 92 · 2026-10-18 23:22:20 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-18T23:22:20Z
fetched_at
2026-10-23T11:04:49Z
stats
{"timeout":0,"harmless":44,"malicious":14,"suspicious":3,"undetected":31}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

eda6a3f1-f2b4-4b64-9512-0bafc66b7611

Final URL

https://bitpro-pulse.com/

HTTP response

200

Navigation history

  • URL
    https://bitpro-pulse.com/
    Status
    200

DOM structure hash

696fb186c820e7a64bd12406721c1a2573ecbc59cfc5440fa97f16d99bd4659e

Document hash

20d0d9c1d7cd77abeb95f5aa6584764785b555a43a5bfe6a28de456f95a6174d

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    bitpro-pulse.com
    Type
    A
    Value
    185.98.60.138

DNSSEC valid

No

IP address

185.98.60.138

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
Internet Domain Service BS Corp
Registered
Updated
Expires
Nameservers
  • ns1.cryptodns.co
  • ns2.cryptodns.co
Original source fields · JSON
Uuid
eda6a3f1-f2b4-4b64-9512-0bafc66b7611
Final url
https://bitpro-pulse.com/
Status
200
History
[
    {
        "url": "https://bitpro-pulse.com/",
        "status": 200
    }
]
DOM structure hash
696fb186c820e7a64bd12406721c1a2573ecbc59cfc5440fa97f16d99bd4659e
Document hash
20d0d9c1d7cd77abeb95f5aa6584764785b555a43a5bfe6a28de456f95a6174d
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "bitpro-pulse.com",
        "type": "A",
        "value": "185.98.60.138"
    }
]
Dnssec valid
false
Ip
185.98.60.138
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Internet Domain Service BS Corp",
    "created": "2024-10-16T09:31:37Z",
    "updated": "2026-05-20T13:59:09Z",
    "expires": "2027-10-16T09:31:37Z",
    "nameservers": [
        "ns1.cryptodns.co",
        "ns2.cryptodns.co"
    ]
}

URLScan

Malicious · engine verdict · score 97

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a167e3-e33a-752a-8ace-531ce1865a85

Final URL

https://bitpro-pulse.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://bitpro-pulse.com/
    From
    http://bitpro-pulse.com/
    Status
    307

IP address

185.98.60.138

Contacted domains

  • fonts.gstatic.com
  • fonts.googleapis.com

Contacted IP addresses

  • 142.251.127.94
  • 142.251.20.95
  • 185.98.60.138

Autonomous systems (ASN)

  • 15169
  • 201064

Server countries

  • US
  • TR

Document hash

20d0d9c1d7cd77abeb95f5aa6584764785b555a43a5bfe6a28de456f95a6174d

Script hashes

  • b1dc3a468eb8949e17762628c68205ee4ffad52ec1cdbe48e3456bf96c1c9603
  • 81a17cfaf5731292df919a903727b86550d2a57e1ad29893dc693ef9c2013113

JavaScript globals

  • __VUE__
  • switcher
  • switcherButton
  • modal
  • btn

Cookies

  • lang_fx

TLS session and certificate

Subject alternative names
  • *.bitpro-pulse.com
  • bitpro-pulse.com
Cipher
AES_128_GCM
Issuer
YE1
Subject
bitpro-pulse.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

736

Registered domain age, days

736

Certificate age, days

34

Certificate validity, days

89

Page requests

56

Provider verdicts

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

HTTP headers

Server
nginx/1.30.1
Content-type
text/html
Original source fields · JSON
Uuid
01a167e3-e33a-752a-8ace-531ce1865a85
Final url
https://bitpro-pulse.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://bitpro-pulse.com/",
        "from": "http://bitpro-pulse.com/",
        "status": 307
    }
]
Ip
185.98.60.138
Contacted domains
[
    "fonts.gstatic.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.251.127.94",
    "142.251.20.95",
    "185.98.60.138"
]
Asns
[
    "15169",
    "201064"
]
Countries
[
    "US",
    "TR"
]
Document hash
20d0d9c1d7cd77abeb95f5aa6584764785b555a43a5bfe6a28de456f95a6174d
Script hashes
[
    "b1dc3a468eb8949e17762628c68205ee4ffad52ec1cdbe48e3456bf96c1c9603",
    "81a17cfaf5731292df919a903727b86550d2a57e1ad29893dc693ef9c2013113"
]
Globals
[
    "__VUE__",
    "switcher",
    "switcherButton",
    "modal",
    "btn"
]
Cookies
[
    "lang_fx"
]
Tls
{
    "san": [
        "*.bitpro-pulse.com",
        "bitpro-pulse.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "bitpro-pulse.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-17T16:37:10Z",
    "valid_from": "2026-09-18T16:37:11Z"
}
Domain age days
736
Apex age days
736
Tls age days
34
Tls valid days
89
Requests
56
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx/1.30.1",
    "content-type": "text/html"
}
Separate monitor record · 2026-10-24 03:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a167e3-e33a-752a-8ace-531ce1865a85
score
0
malicious
false
result_at
2026-10-24T03:30:28Z
enriched_at
2026-10-24T08:17:24Z
source_timestamps
{"urlscan_result_at":"2026-10-24 05:30:28","urlscan_enriched_at":"2026-10-24 10:17:24"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

5 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

98 / 100 · heuristic score · 2 brand references · 1 classifications

Open report
Separate monitor score · 10 / 100 · 2026-10-23T10:20:13Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-10-23T10:20:13Z
source_timestamp
2026-10-23 12:20:13
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
bitpro-pulse.com — Impersonation Phishing Page
ai_description
PhishDestroy flags bitpro-pulse.com as an impersonation phishing site pretending to be a crypto‑education platform, based on the title and security detections.
ai_generated_at
2026-10-23T11:05:57Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider observation dates.

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

Collected source details

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

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

Mail configuration

SPF lookups
0

CAA records

Domain
bitpro-pulse.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
8
Archived days
18
Snapshots per day
0.03
Average page size, bytes
-266998728

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://bitpro-pulse.com/sitemap.xml

Sitemap

Present
Yes
URL count
128

Page title and metadata

Page title
Bitpro Pulse ™ | The Official & Updated Website 2025 🥇
Indexing directives
index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Description
⭐ Bitpro Pulse offers expert cryptocurrency investment education, real-time trading tools, and insights to help you make informed, profitable decisions. ⭐
Twitter card
summary
Canonical URL
https://bitpro-pulse.com/

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
28
Waiting
59
Connection
56
Download
18
Response time, ms
163

TLS connection

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

Ports

Open ports
  • 22
  • 53
  • 80
  • 443

Carbon estimate

Bytes
65673
CO₂, grams
0.0024
Cleaner than, %
31

DNS servers

Nameservers
  • IP address
    185.98.60.138
    Host
    ns1.cryptodns.co
  • IP address
    185.98.60.138
    Host
    ns2.cryptodns.co
DNS zone
bitpro-pulse.com

Location

IP address
185.98.60.138
ASN
201064
Organization
Ideal Hosting Teknoloji A.S.
City
Mahmutbey
Country
TR

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
bitpro-pulse.com

DNS records

A
  • 185.98.60.138
NS
  • ns1.cryptodns.co
  • ns2.cryptodns.co
SOA
Primary nameserver
ns1.cryptodns.co
Hostmaster
admin.cryptodns.co
Serial
2026052113
Refresh, seconds
3600
Retry, seconds
1800
Expiry, seconds
604800
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
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
185.98.60.138
IP version
4

Redirects

Redirect chain
  • https://bitpro-pulse.com

Page links

Internal links
37

Registration record

Registrar
Internet Domain Service BS Corp
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.cryptodns.co
  • ns2.cryptodns.co

HTTP headers

Response headers
Server
nginx/1.30.1
Content-type
text/html
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "bitpro-pulse.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-07-10T20:34:51Z",
    "first": "2024-10-24T22:46:50Z",
    "changes": 8,
    "days_archived": 18,
    "scans_per_day": 0.03,
    "avg_page_bytes": -266998728
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://bitpro-pulse.com/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 128
}
Page title and metadata
{
    "title": "Bitpro Pulse ™ | The Official & Updated Website 2025 🥇",
    "robots": "index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1",
    "description": "⭐ Bitpro Pulse offers expert cryptocurrency investment education, real-time trading tools, and insights to help you make informed, profitable decisions. ⭐",
    "twitterCard": "summary",
    "canonicalUrl": "https://bitpro-pulse.com/"
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 28,
        "wait": 59,
        "connect": 56,
        "download": 18
    },
    "response_ms": 163
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        53,
        80,
        443
    ]
}
Carbon
{
    "bytes": 65673,
    "co2_grams": 0.0024,
    "cleaner_than": 31
}
Dns server
{
    "ns": [
        {
            "ip": "185.98.60.138",
            "host": "ns1.cryptodns.co"
        },
        {
            "ip": "185.98.60.138",
            "host": "ns2.cryptodns.co"
        }
    ],
    "zone": "bitpro-pulse.com"
}
Location
{
    "ip": "185.98.60.138",
    "asn": "201064",
    "org": "Ideal Hosting Teknoloji A.S.",
    "city": "Mahmutbey",
    "country": "TR"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "bitpro-pulse.com"
}
DNS records
{
    "A": [
        "185.98.60.138"
    ],
    "NS": [
        "ns1.cryptodns.co",
        "ns2.cryptodns.co"
    ],
    "SOA": "{\"nsname\": \"ns1.cryptodns.co\", \"hostmaster\": \"admin.cryptodns.co\", \"serial\": 2026052113, \"refresh\": 3600, \"retry\": 1800, \"expire\": 604800, \"minttl\": 300}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "185.98.60.138",
    "family": 4
}
Redirects
{
    "chain": [
        "https://bitpro-pulse.com"
    ]
}
Page links
{
    "internal_count": 37
}
Registration record
{
    "registrar": "Internet Domain Service BS Corp",
    "created": "2024-10-16T09:31:37Z",
    "updated": "2026-05-20T13:59:09Z",
    "expires": "2027-10-16T09:31:37Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.cryptodns.co",
        "ns2.cryptodns.co"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx/1.30.1",
        "content-type": "text/html"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware
View full Cloudflare Radar report

Questions about bitpro-pulse.com

Is bitpro-pulse.com legit?

No. PhishDestroy classifies bitpro-pulse.com as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-23. VirusTotal: 17/92 engines flag it. Treat the site as unsafe.

Is bitpro-pulse.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on bitpro-pulse.com. 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 bitpro-pulse.com?

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 · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded
StateStored capture
HTTP status200
Final URLhttps://bitpro-pulse.com/
Position1 / 5
Open capture Wayback Download
All capture links and hashes (5)

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 23, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Internet Domain Servic… BS(BS)
Abuse contactabuse@internet.bs, abuse@idealhosting.net.tr
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for bitpro-pulse.com →
Hosting abuse contact abuse@idealhosting.net.tr Ideal Hosting Teknoloji A.S. · AS201064
RegistrationCreated Oct 16, 2024 — Expires Oct 16, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 98/1002 brand signals
Submitted URLhttp://bitpro-pulse.com/
Favicon Hash
Case ID
Observed page title
Bitpro Pulse ™ | The Official & Updated Website 2025 🥇
Automated brand references
Across Foundation
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 52 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
185.98.60.138
Network ASN
AS201064
Organization
Ideal Hosting Teknoloji A.S.
Observed location
Mahmutbey, TR
Server header
nginx/1.30.1

Nameservers 2

  • ns1.cryptodns.co
  • ns2.cryptodns.co

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-09-18 16:37:11
Valid until
2026-12-17 16:37:10
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1fea0f50d5690e796dc72cd059f2bcb914cac589709791e760b10df04e9e6280
Certificate names · 2 SANs
  • *.bitpro-pulse.com
  • bitpro-pulse.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 · 185.98.60.138rapiddns.io

Latest Classified Outcome 2026-10-25 12:05:07 UTC

The site was serving its pages at the latest check.

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

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 17 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
DNS8
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of bitpro-pulse.com · checked Oct 23, 2026

80
Needs Work
Performance
FCP
3.3 s
First Contentful Paint
LCP
4.05 s
Largest Contentful Paint
CLS
0.029
Cumulative Layout Shift
TBT
5 ms
Total Blocking Time
SI
3.3 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://bitpro-pulse.com/
Final URL: https://bitpro-pulse.com/
Bitpro Pulse ™ | The Official & Updated Website 2025 🥇
⭐ Bitpro Pulse offers expert cryptocurrency investment education, real-time trading tools, and insights to help you make informed, profitable decisions. ⭐
Response
HTTP 200
HTML body
64.1 KB
Compressed
13.0 KB
Links
42 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.30.1
Content-Type: text/html
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Twitter card: summary
Saved response-header values · 8
Accept-Ranges
bytes
Connection
keep-alive
Content-Length
65673
Content-Type
text/html
Date
Fri, 23 Oct 2026 08:31:19 GMT
Etag
"67818807-10089"
Last-Modified
Fri, 10 Jan 2025 20:50:15 GMT
Server
nginx/1.30.1

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

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

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Domain monitor · First collection record

    Reachable

All retained availability observations15

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

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:05:07.000000
    Evidence SHA-256
    39ba5ba77b7e2d3008233dc6736aa8e2fdf96302d7ea58acb35b9466832ab185
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:05:07
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:05:07.000000
    Evidence SHA-256
    39ba5ba77b7e2d3008233dc6736aa8e2fdf96302d7ea58acb35b9466832ab185
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:05:07
    Evidence reason
    alive_content
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 09:55:07.418941
    Evidence SHA-256
    f29421045a2f0d44850c6f52d6d8bbdf0829af36630a6ed5c83feca2dfe013b6
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 09:55:07.418941
    Evidence reason
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:53:38.000000
    Evidence SHA-256
    ef31baec4d6fe8214672cae8e32fa1447d93e5c4b201684cb84ed9ab01168b9d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:53:38
    Evidence reason
    alive_content
  5. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:53:38.000000
    Evidence SHA-256
    ef31baec4d6fe8214672cae8e32fa1447d93e5c4b201684cb84ed9ab01168b9d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:53:38
    Evidence reason
    alive_content
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:56:25.000000
    Evidence SHA-256
    e89f32a8250ef708dd9a54c088360341152c32b8189288a36469d5de3d45f0d5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:56:25
    Evidence reason
    alive_content
  7. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:56:25.000000
    Evidence SHA-256
    e89f32a8250ef708dd9a54c088360341152c32b8189288a36469d5de3d45f0d5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:56:25
    Evidence reason
    alive_content
  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-24 10:55:03.666169
    Evidence SHA-256
    3db3280361d0b0da230e0746730e29bf48f3dcd3dc85a990b2931515e779b43a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 10:55:03.666169
    Evidence reason
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 01:14:22.000000
    Evidence SHA-256
    2ba7794383dd6c12a74e25aa81b65f25e7d3a6768e7b6f78bda3d455445337dd
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 01:14:22
    Evidence reason
    alive_content
  10. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 01:14:22.000000
    Evidence SHA-256
    2ba7794383dd6c12a74e25aa81b65f25e7d3a6768e7b6f78bda3d455445337dd
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 01:14:22
    Evidence reason
    alive_content
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 13:24:19.000000
    Evidence SHA-256
    c0a8a9f4adbf8353789a5e4d2bd635bea6e71310ea8430a1b4706b40a3e20920
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 13:24:19
    Evidence reason
    alive_content
  12. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 13:24:19.000000
    Evidence SHA-256
    c0a8a9f4adbf8353789a5e4d2bd635bea6e71310ea8430a1b4706b40a3e20920
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 13:24:19
    Evidence reason
    alive_content
  13. 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-23 10:55:00.743425
    Evidence SHA-256
    13567a4852d2464d4e779931d6b58e9a7e4c364f8037d80b364e44546cdc66cf
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 10:55:00.743425
    Evidence reason
  14. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 10:34:31.000000
    Evidence SHA-256
    7472f94c093ecf20967f874c8bffbe6f33ccd2110e248b47e5cae7b1b245938a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 10:34:31
    Evidence reason
  15. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 10:34:31.000000
    Evidence SHA-256
    7472f94c093ecf20967f874c8bffbe6f33ccd2110e248b47e5cae7b1b245938a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 10:34:31
    Evidence reason

Recorded activity

7 entries
  1. AlienVault OTX

    5 community references

    View source
  2. VirusTotal

    17/92 engine detections

    View source
  3. Abuse report sent

    PD-20261023-C5F6C2

    abuse@internet.bs
  4. URLScan

    Page captured

    View source
  5. Cloudflare Radar

    Phishing

    View source
  6. Added to PhishDestroy

    bitpro-pulse.com

    View source
  7. Wayback Machine

    Page archived

    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.

bitpro-pulse.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 17 det. ChainPatrol URLQuery 2 det. SSL Labs Stored certificate dates valid CF Radar Malicious OTX 5 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261023-C5F6C2 Recipient: abuse@internet.bs
Page title stored with report: Bitpro Pulse ™ | The Official & Updated Website 2025 🥇
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?

6 evidence signal groups linked 1 stored notification records Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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 →.

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.

  • 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 bitpro-pulse.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.

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/bitpro-pulse.com"
  title="PhishDestroy threat report for bitpro-pulse.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>