Skip to security report
Analytics Dashboard
Domain security and threat intelligence
bitfinex184.com favicon

bitfinex184.com

In short

bitfinex184.com is a phishing page detected by PhishDestroy on 2026-09-12. Risk: critical (78/100). Registrar: GMO Internet Group. Status: Content unavailable. Hosting: JTIP-AS-AP - JT TELECOM INTERNATIONAL PTE.LTD., SG. VirusTotal: 5/89 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“Bitfinex”

Registrar
GMO Internet Group
Resolved IP
172.81.98.56
Registered
Sep 9, 2026
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 5/89 Spamhaus DBL: DBL_PHISH Scam type: Impersonation
OTX: 4 refs Sep 12, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 5. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
5 / 89
engine detections
Google Safe Browsing
No threat flag
OTX
4
community references
Page captures
2
open gallery
Domain age
43 days
Source evidenceVirusTotal 5 / 89 · OTX 4 references 6 sources

VirusTotal

5 / 89 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

4 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.

Analysis

Critical
VirusTotal
5 / 89
OTX
4 community refs
Page captures
2
Page captures Source results Registration record

PhishDestroy threat report

Overview

bitfinex184.com was a phishing page that copied the cryptocurrency exchange Bitfinex, down to a page title reading simply "Bitfinex". It targeted Bitfinex customers who might land on a lookalike address through a search ad, a message or a mistyped link. PhishDestroy first flagged it on 2026-09-12. The site has been offline since 2026-09-20 and its DNS was still inactive on 2026-10-19.

How the scam works

Exchange impersonation pages show a convincing copy of the real sign-in screen. Whatever the visitor types, including email, password and often a one-time 2FA code, goes straight to the operators. With those details they can log into the genuine Bitfinex account, change security settings and withdraw funds before the owner notices. The number tacked onto the brand name is a common trick that makes the domain look like an official mirror or regional site.

Evidence

On 2026-09-21, five of 89 VirusTotal engines flagged the domain: alphaMountain.ai, Fortinet, Netcraft, PhishFort and SOCRadar. That count is low, but several of these vendors specialise in phishing and brand-abuse detection, so their agreement carries weight. Spamhaus lists the domain in its DBL as phishing, and four AlienVault OTX threat pulses reference it. PhishDestroy carries it on its blocklist.

Infrastructure

The domain was registered on 2026-09-09 through GMO Internet Group (Onamae.com) and was caught three days later. That short gap is typical of throwaway phishing domains set up for a brief campaign. It resolved to 172.81.98.56, an address on JT Telecom International's network (registered in Singapore) and geolocated to Japan. A valid TLS certificate was in place, so the browser padlock gave visitors no warning.

What to do

If you entered Bitfinex credentials on this site, change your Bitfinex password immediately from the official app or a bookmarked address. Reset your 2FA, and change the password anywhere else you reused it. Check your account's login history, active sessions, API keys and withdrawal whitelist, and remove anything you don't recognise. Contact Bitfinex support if you see unauthorised activity. Defenders should block the domain and its hosting IP, search mail and proxy logs for visits since 2026-09-09, and treat Bitfinex-branded domains with numeric suffixes as suspect.

Useful links

urlscan.io scan and screenshotVirusTotal 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-09-11T05:40:13Z

Observed: · Retrieved:

Uuid
01a08efa-e918-74c9-8eb0-8e8c44f77327
Final url
https://bitfinex184.com/wap/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://bitfinex184.com/wap/",
        "from": "https://bitfinex184.com/",
        "status": 302
    }
]
Ip
172.81.98.56
Contacted domains
[
    "cdnjs.cloudflare.com"
]
Contacted IP addresses
[
    "104.17.25.14",
    "172.81.98.56"
]
Asns
[
    "13335",
    "137535"
]
Countries
[
    "JP"
]
Document hash
1cce8fa165826dcfad7622b4bd80d6888308edc99c0f142472d5424fcd56dfee
Script hashes
[
    "ac17ebfd2f332f03125ede8bc97ef3f81d70f54150b66597e5f42c7eef57829f",
    "623378e5155bdf540962f1e718b269b8db12db1a2ee42d74e1d1483853017281",
    "1b7efeb048f7db7f21ea0cd7397d5e5bbbffa031915001a386b4e18f0866d6d9",
    "24be5cc05161f5c72faf5594ba55a0fe0a94e1ad61786f25208cc663bc82f7d1",
    "878daef856219c15d7ea4aee2db7806fb60178935bdb9296c98379096b996339",
    "6e8acf0ae4a999213d22dd787ddbe45bedc09766323544c75d6825bdb8c62e3c",
    "5d206a9e8147c77248438214e185974a70f8214b30f353f12bc33192d24e1d93",
    "a3e80b4ab4f22d77f9d9348d3b668455e1e7a10684c816c951a1956b0f8e5473",
    "91c11cf709d7994441b02ada4dfda08c7bf37558da62bbe52e3db0a2744598f3",
    "3542e26499bfbd6f84fa973b3923a52ae61fee24b092bbadec76314ab282c12c"
]
Globals
[
    "webpackChunkexchange",
    "clearImmediate",
    "setImmediate",
    "eventBus",
    "_PageAccelerator",
    "pageAccelerator"
]
Storage keys
[
    "@@",
    "lang",
    "vuex",
    "categoryNum"
]
Tls
{
    "san": [
        "bitfinex180.com",
        "bitfinex181.com",
        "bitfinex182.com",
        "bitfinex183.com",
        "bitfinex184.com",
        "bitfinex185.com",
        "bitfinex186.com",
        "bitfinex187.com",
        "bitfinex188.com",
        "bitfinex189.com"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "bitfinex185.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-09T11:51:41Z",
    "valid_from": "2026-09-10T11:51:42Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
238
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000"
}
Cloudflare Radar · 2026-09-14T07:16:40Z

Observed: · Retrieved:

Uuid
6cef2ea3-8090-4876-838e-ef4bcfdba4a7
Final url
https://bitfinex184.com/wap/
Status
200
Redirected
same-domain
History
[
    {
        "url": "https://bitfinex184.com/",
        "status": 302
    },
    {
        "url": "https://bitfinex184.com/wap/",
        "status": 200
    }
]
DOM structure hash
336fff67d32977be972e92385bc2385cfe2a570125420568d94998ce8dbc8f0a
Document hash
a36e7919c7d81d905e80febfdaeb4367f5466c895492f8cfcca96ac01474176d
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "bitfinex184.com",
        "type": "A",
        "value": "172.81.98.56"
    }
]
Dnssec valid
false
Ip
172.81.98.56
Registration record
{
    "registrar": "GMO Internet Group, Inc. d/b/a Onamae.com",
    "created": "2026-09-09T12:48:51Z",
    "updated": "2026-09-09T12:49:04Z",
    "expires": "2027-09-09T12:48:51Z",
    "nameservers": [
        "a1.share-dns.com",
        "b1.share-dns.net"
    ]
}
VirusTotal · 2026-09-12T00:12:44Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 4,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "PhishFort": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)"
}
Registrar
GMO Internet Group, Inc. d/b/a Onamae.com
Created
2026-09-09T12:48:51Z
Expires
2027-09-09T12:48:51Z
Updated
2026-09-09T12:49:04Z
First seen
2026-09-10T08:19:43Z
DNS records
[
    {
        "ttl": 600,
        "type": "A",
        "value": "172.81.98.56"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "b.share-dns.net"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "a.share-dns.com"
    },
    {
        "ttl": 600,
        "type": "SOA",
        "rname": "master.share-dns.com",
        "value": "a.share-dns.com"
    }
]
Dns at
2026-09-12T00:13:02Z
Jarm
3fd3fd0003fd3fd00042d42d0000002059a3b916699461c5923779b77cf06b
Certificate
{
    "san": [
        "bitfinex180.com",
        "bitfinex181.com",
        "bitfinex182.com",
        "bitfinex183.com",
        "bitfinex184.com",
        "bitfinex185.com",
        "bitfinex186.com",
        "bitfinex187.com",
        "bitfinex188.com",
        "bitfinex189.com"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "6eda5d75724a1795c25856a8c650a90f8",
    "sha256": "029089892575ced79820836eb2b1ba44863d11b160764f5c7065333494c401d7",
    "subject": "bitfinex185.com",
    "valid_to": "2026-12-09T11:51:41Z",
    "valid_from": "2026-09-10T11:51:42Z"
}
Registration record
{
    "registrar": "GMO Internet Group, Inc. d/b/a Onamae.com",
    "registrar_iana_id": "49",
    "registrar_url": "https://internet.gmo/",
    "created": "2026-09-09T12:48:51Z",
    "updated": "2026-09-09T12:49:04Z",
    "expires": "2027-09-09T12:48:51Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "a1.share-dns.com",
        "b1.share-dns.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-09-08T15:00:00Z",
        "last changed": "2026-09-09T12:59:04Z",
        "registration": "2026-09-09T03:48:51Z",
        "registrar expiration": "2027-09-08T15:00:00Z",
        "last update of RDAP database": "2026-09-10T08:19:43Z"
    }
}

Questions about bitfinex184.com

Is bitfinex184.com legit?

No. PhishDestroy classifies bitfinex184.com as a phishing page (risk: critical, 78/100); it was first detected on 2026-09-12. VirusTotal: 5/89 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is bitfinex184.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on bitfinex184.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 bitfinex184.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 · 2 captures

Primary capture 1 / 2
SourcePrimary capture
Recorded2026-09-12 04:40 UTC
StateStored capture
Position1 / 2
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar GMO Internet Group
Abuse contact["abuse@internet.gmo"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for bitfinex184.com →
RegistrationCreated Sep 9, 2026 (43d · New) — Expires Sep 9, 2027
Time to First Unavailability 8 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 12, 2026
Observed page title
Bitfinex
TLS Certificate
Issued by YR2 · stored validity ends in 47 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
172.81.98.56
Network ASN
AS137535
Organization
JT TELECOM INTERNATIONAL PTE.LTD.
Observed location
Tokyo, JP
Server header
nginx

Nameservers 1

  • b1.share-dns.net

Location describes the IP network.

TLS certificate

Issuer
YR2
Valid from
2026-09-10 11:51:42
Valid until
2026-12-09 11:51:41
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint029089892575ced79820836eb2b1ba44863d11b160764f5c7065333494c401d7
Certificate names · 10 SANs
  • bitfinex180.com
  • bitfinex181.com
  • bitfinex182.com
  • bitfinex183.com
  • bitfinex184.com
  • bitfinex185.com
  • bitfinex186.com
  • bitfinex187.com
  • bitfinex188.com
  • bitfinex189.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 · 172.81.98.56rapiddns.io

Latest Classified Outcome 2026-10-21 14:53:36 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-21 01:16:00 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-12 05:28:11 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-12 05:28:11 UTC → 2026-09-30 16:14:55 UTC · 442.78h midpoint estimate ≈ 2026-09-21 10:51:33 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

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

Availability observations

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

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

Stored observation history14

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→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 9
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/6cef2ea3-8090-4876-838e-ef4bcfdba4a7

  8. Availability monitor · Recorded state

    Reachable→Unavailable

  9. Availability monitor · First collection record

    Reachable

Recorded activity

4 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    5/89 engine detections

    View source
  4. Added to PhishDestroy

    bitfinex184.com

    View source

Community intelligence

1 community report

CategoryIMPERSONATION

Brand abuse: impersonation, fake affiliation, investment scam, impersonating Bitfinex

Check for cloaking

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

bitfinex184.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 5 det. ChainPatrol ChainAbuse 1 report URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Third-Party Detection — ChainAbuse
1 report filed for bitfinex184.com · category: Impersonation · source checked
Flagged by automated brand-abuse detection on Sep 11, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

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 bitfinex184.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

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