binance.com was registered on 31 Dec 1984 and is hosted on AS16509 Amazon.com Inc. in Japan. Its SSL certificate from DigiCert Inc expired on 13 Jan 2026, and the site does not support HTTP/3. WOT's community rates its safety excellent (83/100).
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Is binance.com’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| India | 10.3% | 9,146,806 | 20.5% | 79.5% |
| Russia | 8.4% | 7,514,220 | 81.9% | 18.1% |
| Türkiye | 5.3% | 4,721,063 | 48.3% | 51.7% |
| United States | 4.2% | 3,721,061 | 62.9% | 37.1% |
| United Kingdom | 4% | 3,534,458 | 41% | 59% |
Every IP address binance.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| binance.com | 52.197.66.242 | 17 |
| binance.com | 54.248.61.176 | 17 |
| binance.com | 57.181.54.203 | 17 |
| Host | Mail server | TTL |
|---|---|---|
| binance.com | 1 aspmx.l.google.com | 100 |
| binance.com | 5 alt1.aspmx.l.google.com | 100 |
| binance.com | 5 alt2.aspmx.l.google.com | 100 |
| binance.com | 10 aspmx2.googlemail.com | 100 |
| binance.com | 10 aspmx3.googlemail.com | 100 |
| Host | Name server | TTL |
|---|---|---|
| binance.com | ns-1319.awsdns-36.org | 60 |
| binance.com | ns-1701.awsdns-20.co.uk | 60 |
| binance.com | ns-234.awsdns-29.com | 60 |
| binance.com | ns-735.awsdns-27.net | 60 |
| Host | Text | TTL |
|---|---|---|
| binance.com | "0c095c37-7040-413b-8cf7-09dca0c85bf5=71fd4d87c99f04fd995b7aad459560824dc7b4039a8631ba4386ded49e47924f" | 180 |
| binance.com | "6gr8gw6zgdmf1590qh3qzcnj3crq5f6x" | 180 |
| binance.com | "brave-ledger-verification=81a47ec702afe8d8eeec47aadad537bd0086adf6dbce54466ad507721328a565" | 180 |
| binance.com | "ca3-db034fa91a494d8da7d577e5cbae92c9" | 180 |
| binance.com | "DirectFedAuthUrl=https://binance-devops.okta.com/app/binance-devops_azure_1/exko7oeeoxYlABN6A4x7/sso/saml" | 180 |
| binance.com | "DirectFedAuthUrl=https://binance.okta.com/app/binance_azureportal_1/exk1brl3su69WMFtd358/sso/saml" | 180 |
| binance.com | "docusign=e41ac1a2-97ba-4a73-9ab4-80d67b03b838" | 180 |
| binance.com | "facebook-domain-verification=n2otwpnja9hvycz7vq72n7zcbsjczn" | 180 |
| binance.com | "fARyevT0IDAfLqRcPFTyHCyW" | 180 |
| binance.com | "g161fcffczllxspkxcj215xnhg2ccy5c" | 180 |
| binance.com | "google-site-verification=FbfML-3x7_Lw0ZNr0jiEpAGipS70RD76Gni7yrwp27c" | 180 |
| binance.com | "google-site-verification=N-cLYfh9dATCmYDwP_yu_8hTUzNLEPs9GD8_V0gUmeg" | 180 |
| binance.com | "google-site-verification=oAHlszxw85VnJAPSrnDedi0Bl_BZTY5G1X_ZTDVHSpM" | 180 |
| binance.com | "google-site-verification=zUAcB1Xn4N69hl_cQSn3Mwj4TGaLSRi0U9VdKsJCfRQ" | 180 |
| binance.com | "keybase-site-verification=BYsJCGB6nMaHAsZmwgOKRvsBBDUFkwWptpyNCvQxQms" | 180 |
| binance.com | "mongodb-site-verification=T96XfgL8SO5MnMTaZ115HKHJ4io6nLH7" | 180 |
| binance.com | "mongodb-site-verification=WUb0QnhXkP1bJNTZfiTdSgstUfq9WI8q" | 180 |
| binance.com | "MS=D31FF5D988DDDB7153A115F1827B162A84C69F6B" | 180 |
| binance.com | "onetrust-domain-verification=96e9abfaee504c80833cbb93d913b1e8" | 180 |
| binance.com | "v=spf1 include:_spf.google.com -all" | 180 |
| binance.com | "wallet-connect-dns-verification=71fd4d87c99f04fd995b7aad459560824dc7b4039a8631ba4386ded49e47924f" | 180 |
| Host | Start of authority | TTL |
|---|---|---|
| binance.com | ns-735.awsdns-27.net awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
No reviews yet. Used binance.com? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
WOT's community rates binance.com excellent for safety (83/100). Its SSL certificate expired on 13 Jan 2026. See Security →
binance.com was registered on 31 Dec 1984, making it 41 years old. See Overview →
binance.com is served from 3 IP addresses, mainly on AS16509 Amazon.com Inc. in Japan. See Hosting →
Raw registry data for binance.com. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: whois.verisign-grs.com domain: COM organisation: VeriSign Global Registry Services address: 12061 Bluemont Way address: Reston VA 20190 address: United States of America (the) contact: administrative name: Registry Customer Service organisation: VeriSign Global Registry Services address: 12061 Bluemont Way address: Reston VA 20190 address: United States of America (the) phone: +1 703 925-6999 fax-no: +1 703 948 3978 e-mail: [email protected] contact: technical name: Registry Customer Service organisation: VeriSign Global Registry Services address: 12061 Bluemont Way address: Reston VA 20190 address: United States of America (the) phone: +1 703 925-6999 fax-no: +1 703 948 3978 e-mail: [email protected] nserver: A.GTLD-SERVERS.NET 192.5.6.30 2001:503:a83e:0:0:0:2:30 nserver: B.GTLD-SERVERS.NET 192.33.14.30 2001:503:231d:0:0:0:2:30 nserver: C.GTLD-SERVERS.NET 192.26.92.30 2001:503:83eb:0:0:0:0:30 nserver: D.GTLD-SERVERS.NET 192.31.80.30 2001:500:856e:0:0:0:0:30 nserver: E.GTLD-SERVERS.NET 192.12.94.30 2001:502:1ca1:0:0:0:0:30 nserver: F.GTLD-SERVERS.NET 192.35.51.30 2001:503:d414:0:0:0:0:30 nserver: G.GTLD-SERVERS.NET 192.42.93.30 2001:503:eea3:0:0:0:0:30 nserver: H.GTLD-SERVERS.NET 192.54.112.30 2001:502:8cc:0:0:0:0:30 nserver: I.GTLD-SERVERS.NET 192.43.172.30 2001:503:39c1:0:0:0:0:30 nserver: J.GTLD-SERVERS.NET 192.48.79.30 2001:502:7094:0:0:0:0:30 nserver: K.GTLD-SERVERS.NET 192.52.178.30 2001:503:d2d:0:0:0:0:30 nserver: L.GTLD-SERVERS.NET 192.41.162.30 2001:500:d937:0:0:0:0:30 nserver: M.GTLD-SERVERS.NET 192.55.83.30 2001:501:b1f9:0:0:0:0:30 ds-rdata: 19718 13 2 8acbb0cd28f41250a80a491389424d341522d946b0da0c0291f2d3d771d7805a whois: whois.verisign-grs.com status: ACTIVE remarks: Registration information: http://www.verisigninc.com created: 1985-01-01 changed: 2023-12-07 source: IANA
The first response from http://www.binance.com, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with binance.com. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.