bitget.directory was registered on 13 Nov 2013. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
0 of 5 protections set up
No SPF record: any server can send mail that claims to come from this domain.
—No key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
We couldn't read an SSL certificate on port 443 when we last analysed bitget.directory. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
301 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| bltget.fun | Look-alike characters | 15 Sept 2026 | Checking… | Report → |
| bltget.top | Look-alike characters | 15 Sept 2026 | Checking… | Report → |
| bltget.art | Look-alike characters | 13 Sept 2026 | Checking… | Report → |
| bltget.work | Look-alike characters | 13 Sept 2026 | Checking… | Report → |
| bltget.fit | Look-alike characters | 23 Aug 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is bitget.directory’s name taken on other extensions?
No reviews yet. Used bitget.directory? 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.
bitget.directory has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
bitget.directory was registered on 13 Nov 2013, making it 12 years old. See Overview →
Raw registry data for bitget.directory. 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: domain: DIRECTORY organisation: Binky Moon, LLC address: c/o Identity Digital Inc. address: 10500 NE 8th Street, Suite 750 address: Bellevue WA 98004 address: United States of America (the) contact: administrative name: Vice President, Engineering organisation: Identity Digital Inc. address: 10500 NE 8th Street, Suite 750 address: Bellevue WA 98004 address: United States of America (the) phone: +1.425.298.2200 fax-no: +1.425.671.0020 e-mail: [email protected] contact: technical name: Senior Director, DNS Infrastructure Group organisation: Identity Digital Limited address: c/o Identity Digital Inc. address: 10500 NE 8th Street, Suite 750 address: Bellevue WA 98004 address: United States of America (the) phone: +1.425.298.2200 fax-no: +1.425.671.0020 e-mail: [email protected] nserver: V0N0.NIC.DIRECTORY 2a01:8840:1e:0:0:0:0:11 65.22.28.11 nserver: V0N1.NIC.DIRECTORY 2a01:8840:1f:0:0:0:0:11 65.22.29.11 nserver: V0N2.NIC.DIRECTORY 2a01:8840:20:0:0:0:0:11 65.22.30.11 nserver: V0N3.NIC.DIRECTORY 161.232.14.11 2a01:8840:f8:0:0:0:0:11 nserver: V2N0.NIC.DIRECTORY 2a01:8840:21:0:0:0:0:11 65.22.31.11 nserver: V2N1.NIC.DIRECTORY 161.232.15.11 2a01:8840:f9:0:0:0:0:11 ds-rdata: 59725 8 2 0d647c2701e4d9988d38939e1e372c77dbc0f76d21c8d2bd6e40a21fbd4441a3 whois: status: ACTIVE remarks: Registration information: https://www.identity.digital/ created: 2013-11-13 changed: 2025-10-07 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with bitget.directory. 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.
We couldn't find an IP address for bitget.directory's web or mail servers to check.
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.
No changes seen since we started recording on 19 Oct 2026.