Skip to security report
Analytics Dashboard
Domain security and threat intelligence
bitgpt.org favicon

bitgpt.org

In short

bitgpt.org is a Celer impersonation 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: 15/92 engines flag it. Do not enter credentials or connect a wallet.

“Bit GPT ™ | The Official & Updated Website 2025 🥇”

Registrar
Internet Domain Servic…
Resolved IP
185.98.60.138
Registered
Mar 30, 2023
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 15/92 Automated brand label: Celer
OTX: 1 ref Oct 23, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 15. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
15 / 92
engine detections
Google Safe Browsing
No threat flag
URLQuery
2
detections
OTX
1
community references
Page captures
5
open gallery
Domain age
1302 days
Reports sent
1
view timeline
Source evidenceVirusTotal 15 / 92 · OTX 1 references 6 sources

VirusTotal

15 / 92 engine detections

Open report

OTX

1 community reference

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
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware
View full Cloudflare Radar report

Analysis

Critical
VirusTotal
15 / 92
OTX
1 community ref
Page captures
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy classified bitgpt.org as a suspicious domain after multiple security vendors flagged it as malicious. The domain was first observed by PhishDestroy on 2026-10-23. The recorded page title was “Bit GPT ™ | The Official & Updated Website 2025 🥇” and the site returned HTTP 200 on the same check date.

How the scam works

Because the listing is based on vendor detections rather than observed malicious behavior, no concrete scam technique is demonstrated on this page. In general, domains with similar phishing or malware labels may be used to lure users into revealing credentials, installing unwanted software, or interacting with fraudulent cryptocurrency services, but such activity was not seen here.

Evidence

VirusTotal scanned bitgpt.org on 2026-10-18 and recorded 13 malicious and 2 suspicious detections from 92 engines, for a total of 15 hits. Google Safe Browsing checked the domain on 2026-10-23 and returned no warning. urlscan captured the site on 2026-07-30; its engine verdict was malicious with a score of 89, while the overall verdict was clean. PhishDestroy’s internal blocklist marked the domain as true on 2026-10-23, no external blocklists listed it, and OTX showed one pulse referencing the domain on 2026-10-23.

Infrastructure

bitgpt.org was registered on 2023-03-30 through Internet Domain Service BS Corp and used the nameservers ns1.cryptodns.co and ns2.cryptodns.co. The recorded IP was 185.98.60.138, which was associated with Ideal Hosting Teknoloji A.S. in Turkey (ASN 201064). The TLS certificate, issued by Let’s Encrypt, covered *.bitgpt.org and was valid until 2026-12-17; DNSSEC was not enabled.

What to do

Visitors should avoid entering any credentials, downloading files, or interacting with cryptocurrency features on this site; if such data was already submitted, change the associated passwords and monitor accounts for unauthorized activity. Defenders can block bitgpt.org at DNS or proxy level and add the domain to relevant threat‑intelligence feeds. Any interaction should be reported to PhishDestroy for further analysis.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-23T05:33:00Z)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-23T05:43:17Z

Observed: · Retrieved:

Uuid
01a16748-ce8e-7022-b7ff-8095ef063e1a
Final url
https://bitgpt.org/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://bitgpt.org/",
        "from": "http://bitgpt.org/",
        "status": 307
    }
]
Ip
185.98.60.138
Contacted domains
[
    "fonts.gstatic.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.251.14.94",
    "142.251.127.95",
    "185.98.60.138"
]
Asns
[
    "15169",
    "201064"
]
Countries
[
    "US",
    "TR"
]
Document hash
dd24127022d2e6a78f29d97a7debed6ee2fd570b9cbd2468c3a1184ee1c5446a
Script hashes
[
    "b1dc3a468eb8949e17762628c68205ee4ffad52ec1cdbe48e3456bf96c1c9603",
    "81a17cfaf5731292df919a903727b86550d2a57e1ad29893dc693ef9c2013113"
]
Globals
[
    "__VUE__",
    "switcher",
    "switcherButton",
    "modal",
    "btn"
]
Cookies
[
    "lang_fx"
]
Tls
{
    "san": [
        "*.bitgpt.org",
        "bitgpt.org"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "bitgpt.org",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-17T16:27:33Z",
    "valid_from": "2026-09-18T16:27:34Z"
}
Domain age days
1302
Apex age days
1302
Tls age days
34
Tls valid days
89
Requests
56
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 94,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx/1.30.1",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-10-23T05:33:00Z

Observed: · Retrieved:

Uuid
f9638f05-59d5-456e-a599-e06c5d94c152
Final url
https://bitgpt.org/
Status
200
History
[
    {
        "url": "https://bitgpt.org/",
        "status": 200
    }
]
DOM structure hash
065b2b291bf490b6c43949d0401aedc0c67cc88eade93d56554306b0ac5f0dd8
Document hash
dd24127022d2e6a78f29d97a7debed6ee2fd570b9cbd2468c3a1184ee1c5446a
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "bitgpt.org",
        "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": "2023-03-30T12:00:50Z",
    "updated": "2026-08-12T00:13:17Z",
    "expires": "2027-03-30T12:00:50Z",
    "nameservers": [
        "ns1.cryptodns.co",
        "ns2.cryptodns.co"
    ]
}
VirusTotal · 2026-10-18T11:52:48Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 13,
    "suspicious": 2,
    "undetected": 32
}
Vendor labels
{
    "ESET": "suspicious",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "malware",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Created
2023-03-30T00:00:00Z
Updated
2026-04-18T00:00:00Z
First seen
2023-11-21T11:30:16Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.cryptodns.co"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.cryptodns.co"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "admin.cryptodns.co",
        "value": "ns1.cryptodns.co"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "185.98.60.138"
    }
]
Dns at
2026-10-18T11:58:05Z
Jarm
1dd40d40d00040d00042d43d000000831b6af40378e2dd35eeac4e9311926e
Certificate
{
    "san": [
        "*.bitgpt.org",
        "bitgpt.org"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "54e1ee65fe16a0cdf025075334488806211",
    "sha256": "cbca6b2bc4b62b288e3f0d3098b7d98347f340e8a23f821e3938f420d99615a9",
    "subject": "bitgpt.org",
    "valid_to": "2026-12-17T16:27:33Z",
    "valid_from": "2026-09-18T16:27:34Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-03-30T12:00:50Z",
        "last changed": "2026-05-20T13:55:10Z",
        "registration": "2023-03-30T12:00:50Z",
        "registrar expiration": "2027-03-30T12:00:50Z",
        "last update of RDAP database": "2026-10-16T23:29:47Z"
    },
    "registrar": "Internet Domain Service BS Corp.",
    "registrar_iana_id": "2487"
}
Website checks · 2026-10-23T05:35:25Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "bitgpt.org"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-23T05:25:31Z",
    "first": "2023-04-26T16:05:12Z",
    "changes": 54,
    "days_archived": 63,
    "scans_per_day": 0.05,
    "avg_page_bytes": 12453
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://bitgpt.org/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 128
}
Page title and metadata
{
    "title": "Bit GPT ™ | The Official & Updated Website 2025 🥇",
    "robots": "index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1",
    "description": "🚀Master crypto investments with Bit GPT: Get educated and trade smarter on our comprehensive cryptocurrency platform.🚀",
    "twitterCard": "summary",
    "canonicalUrl": "https://bitgpt.org/"
}
Trackers
{
    "requests": 51,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 3
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 323,
        "tls": 22,
        "wait": 40,
        "connect": 26,
        "download": 29
    },
    "response_ms": 440
}
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": 63301,
    "co2_grams": 0.0023,
    "cleaner_than": 32
}
Dns server
{
    "ns": [
        {
            "ip": "185.98.60.138",
            "host": "ns2.cryptodns.co"
        },
        {
            "ip": "185.98.60.138",
            "host": "ns1.cryptodns.co"
        }
    ],
    "zone": "bitgpt.org"
}
Cookies
{
    "cookies": [
        {
            "name": "lang_fx"
        }
    ]
}
Location
{
    "ip": "185.98.60.138",
    "asn": "201064",
    "org": "Ideal Hosting Teknoloji A.S.",
    "city": "Mahmutbey",
    "country": "TR"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "bitgpt.org"
}
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://bitgpt.org"
    ]
}
Tech stack
{
    "technologies": [
        "Vue.js",
        "Nginx",
        "Google Font API"
    ]
}
Page links
{
    "internal_count": 37
}
Registration record
{
    "registrar": "Internet Domain Service BS Corp",
    "created": "2023-03-30T12:00:50Z",
    "updated": "2026-08-12T00:13:17Z",
    "expires": "2027-03-30T12:00:50Z",
    "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"
    }
}

Questions about bitgpt.org

Is bitgpt.org legit?

No. PhishDestroy classifies bitgpt.org as a Celer impersonation page (risk: critical, 100/100); it was first detected on 2026-10-23. VirusTotal: 15/92 engines flag it. Treat the site as unsafe.

Is bitgpt.org safe to connect a wallet?

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

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
Recorded2026-10-23 05:45 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://bitgpt.org/
Position1 / 5
Open capture Wayback Download

Domain details

Domain
IP Reputation abuse score 0/100 0 reports checked Oct 23, 2026
Registrar Internet Domain Servic…
Abuse contactabuse@idealhosting.net.tr, registry@key-systems.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for bitgpt.org →
RegistrationCreated Mar 30, 2023 — Expires Mar 30, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 93/1005 brand signals
Submitted URLhttp://bitgpt.org/
Favicon Hash
Case ID
Observed page title
Bit GPT ™ | The Official & Updated Website 2025 🥇
Automated brand references
Celer Cosmos Curve Foundation PayPal
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 55 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 / YE2
Valid from
2026-09-18 16:27:34
Valid until
2026-12-17 16:27:33
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintcbca6b2bc4b62b288e3f0d3098b7d98347f340e8a23f821e3938f420d99615a9
Certificate names · 2 SANs
  • *.bitgpt.org
  • bitgpt.org

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
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

15 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
Chong Lua Dao
ESET
Emsisoft
Forcepoint ThreatSeeker
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of bitgpt.org · checked Oct 23, 2026

75
Needs Work
Performance
FCP
3.3s
First Contentful Paint
LCP
4.96s
Largest Contentful Paint
CLS
0.029
Cumulative Layout Shift
TBT
18ms
Total Blocking Time
SI
3.37s
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://bitgpt.org/
Final URL: https://bitgpt.org/
Bit GPT ™ | The Official & Updated Website 2025 🥇
🚀Master crypto investments with Bit GPT: Get educated and trade smarter on our comprehensive cryptocurrency platform.🚀
Response
HTTP 200
HTML body
61.8 KB
Compressed
13.2 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
63301
Content-Type
text/html
Date
Fri, 23 Oct 2026 05:27:00 GMT
Etag
"678160c2-f745"
Last-Modified
Fri, 10 Jan 2025 18:02:42 GMT
Server
nginx/1.30.1

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.

Recorded activity

6 entries
  1. Abuse report sent

    PD-20261023-573699

    abuse@idealhosting.net.tr
  2. URLScan

    Page captured

    View source
  3. AlienVault OTX

    1 community references

    View source
  4. Google Safe Browsing

    No threat flag

    View source
  5. VirusTotal

    15/92 engine detections

    View source
  6. Added to PhishDestroy

    bitgpt.org

    View source

Check for cloaking

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

bitgpt.org

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 15 det. ChainPatrol URLQuery 2 det. SSL Labs Stored certificate dates valid CF Radar Malicious OTX 1 ref WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261023-573699 Recipient: abuse@idealhosting.net.tr
Page title stored with report: Bit GPT ™ | 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
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 bitgpt.org)
  • 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/bitgpt.org"
  title="PhishDestroy threat report for bitgpt.org"
  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>