sete.capital was registered on 2 Apr 2014 and is hosted on AS40034 in British Virgin Islands. 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 sete.capital. Refresh the analysis to check again.
408 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| este.capital | Typo | 25 Oct 2026 | Checking… | Report → |
| se7e.app | Look-alike characters | 23 Aug 2026 | Checking… | Report → |
| seet.agency | Typo | 20 Oct 2026 | Checking… | Report → |
| seet.mx | Typo | 19 Oct 2026 | Checking… | Report → |
| seet.fun | Typo | 9 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is sete.capital’s name taken on other extensions?
Every IP address sete.capital resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| sete.capital | 208.91.197.27 | 7200 |
| Host | Name server | TTL |
|---|---|---|
| sete.capital | ns1.domain.com | 7200 |
| sete.capital | ns2.domain.com | 7200 |
| Host | Start of authority | TTL |
|---|---|---|
| sete.capital | NS1.DOMAIN.COM [email protected] 124072310 10800 3600 604800 3600 | 7200 |
Other domains served from 208.91.197.27. Normal for shared hosting and CDNs.
No reviews yet. Used sete.capital? 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.
sete.capital has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
sete.capital was registered on 2 Apr 2014, making it 12 years old. See Overview →
sete.capital is served from 1 IP address, mainly on AS40034 in British Virgin Islands. See Hosting →
Raw registry data for sete.capital. 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.capital domain: CAPITAL organisation: Binky Moon, LLC address: c/o Identity Digital Limited 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 Limited 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: 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.CAPITAL 2a01:8840:1e:0:0:0:0:10 65.22.28.10 nserver: V0N1.NIC.CAPITAL 2a01:8840:1f:0:0:0:0:10 65.22.29.10 nserver: V0N2.NIC.CAPITAL 2a01:8840:20:0:0:0:0:10 65.22.30.10 nserver: V0N3.NIC.CAPITAL 161.232.14.10 2a01:8840:f8:0:0:0:0:10 nserver: V2N0.NIC.CAPITAL 2a01:8840:21:0:0:0:0:10 65.22.31.10 nserver: V2N1.NIC.CAPITAL 161.232.15.10 2a01:8840:f9:0:0:0:0:10 ds-rdata: 9469 8 2 e4832b3a24031e377c4d82a22c87efadee41fac941fd1fac7a2ab5ecc9b821a0 whois: whois.nic.capital status: ACTIVE remarks: Registration information: https://www.identity.digital/ created: 2014-04-03 changed: 2023-09-12 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with sete.capital. 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.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.