blokee.ai was registered with whois.nic.ai on 16 Feb 1995 and is hosted on AS16509 Amazon.com Inc. in Korea (Republic of). 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.
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 blokee.ai. Refresh the analysis to check again.
28 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| blokes.golf | Typo | 15 Oct 2026 | Checking… | Report → |
| blokes.si | Typo | 15 Oct 2026 | Checking… | Report → |
| bookee.ru | Typo | 15 Oct 2026 | Checking… | Report → |
| bloker.online | Typo | 10 Oct 2026 | Checking… | Report → |
| blokes.uk | Typo | 7 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is blokee.ai’s name taken on other extensions?
Every IP address blokee.ai resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| blokee.ai | 15.165.28.43 | 53 |
| blokee.ai | 52.79.172.226 | 53 |
| Host | Mail server | TTL |
|---|---|---|
| blokee.ai | 1 aspmx.l.google.com | 60 |
| blokee.ai | 5 alt1.aspmx.l.google.com | 60 |
| blokee.ai | 5 alt2.aspmx.l.google.com | 60 |
| blokee.ai | 10 alt3.aspmx.l.google.com | 60 |
| blokee.ai | 10 alt4.aspmx.l.google.com | 60 |
| Host | Name server | TTL |
|---|---|---|
| blokee.ai | ns-1444.awsdns-52.org | 60 |
| blokee.ai | ns-2039.awsdns-62.co.uk | 60 |
| blokee.ai | ns-509.awsdns-63.com | 60 |
| blokee.ai | ns-639.awsdns-15.net | 60 |
| Host | Start of authority | TTL |
|---|---|---|
| blokee.ai | ns-2039.awsdns-62.co.uk awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 60 |
No reviews yet. Used blokee.ai? 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.
blokee.ai has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
blokee.ai is registered through whois.nic.ai. See WHOIS →
blokee.ai was registered on 16 Feb 1995, making it 31 years old. See Overview →
blokee.ai is served from 2 IP addresses, mainly on AS16509 Amazon.com Inc. in Korea (Republic of). See Hosting →
Raw registry data for blokee.ai. 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.nic.ai domain: AI organisation: Government of Anguilla address: Coronation Avenue, PO Box 60 address: The Valley AI2640 address: Anguilla contact: administrative name: Telecommunications Officer organisation: Government of Anguilla, Ministry of Infrastructure, Communications and Utilities address: Coronation Avenue, PO Box 60 address: The Valley AI2640 address: Anguilla phone: +1 264 497 5233 e-mail: telecommunications.office@gov.ai contact: technical name: Vincent Cate organisation: DataHaven.Net Ltd. address: 949 Stoney Ground address: The Valley AI2640 address: Anguilla phone: +1 264 497 3255 e-mail: vincecate@gmail.com nserver: A.LACTLD.ORG 200.0.68.10 2801:14:a000:0:0:0:0:10 nserver: ANYCASTDNS1-CZ.NIC.AI 185.28.194.194 nserver: ANYCASTDNS2-CZ.NIC.AI 185.38.108.108 2a00:fea0:dead:0:0:0:0:beef nserver: PCH.WHOIS.AI 2001:500:14:6123:ad:0:0:1 204.61.216.123 whois: whois.nic.ai status: ACTIVE remarks: Registration information: http://whois.ai created: 1995-02-16 changed: 2022-07-20 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with blokee.ai. 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.