designity.build was registered with whois.nic.build on 9 Jan 2014 and is hosted on AS396982 in United States. 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 designity.build. Refresh the analysis to check again.
18 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| designity.eu | Other extension | 5 Oct 2026 | Checking… | Report → |
| designify.design | Typo | 11 Sept 2026 | Checking… | Report → |
| designify.space | Typo | 9 Sept 2026 | Checking… | Report → |
| designify.shop | Typo | 26 Aug 2026 | Checking… | Report → |
| designit.si | Typo | 11 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is designity.build’s name taken on other extensions?
Every IP address designity.build resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| designity.build | 34.102.136.180 | 600 |
| Host | Name server | TTL |
|---|---|---|
| designity.build | ns11.domaincontrol.com | 3600 |
| designity.build | ns12.domaincontrol.com | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| designity.build | ns11.domaincontrol.com dns.jomax.net 2023060700 28800 7200 604800 600 | 3600 |
Other domains served from 34.102.136.180. Normal for shared hosting and CDNs.
No reviews yet. Used designity.build? 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.
designity.build has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
designity.build is registered through whois.nic.build. See WHOIS →
designity.build was registered on 9 Jan 2014, making it 12 years old. See Overview →
designity.build is served from 1 IP address, mainly on AS396982 in United States. See Hosting →
Raw registry data for designity.build. 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.build domain: BUILD organisation: Plan Bee LLC address: 2800 28th St., Suite 170 address: Santa Monica CA 90405 address: United States of America (the) contact: administrative name: George Minardos organisation: Plan Bee LLC address: 2800 28th St., Suite 170 address: Santa Monica CA 90405 address: United States of America (the) phone: +01 310 450-6900 fax-no: +01 310 450 6988 e-mail: george@dotbuild.co contact: technical name: CTO organisation: CentralNic address: Saddlers House, 4th Floor address: 44 Gutter Lane address: London EC2V 6BR address: United Kingdom of Great Britain and Northern Ireland (the) phone: +44 20 33 88 0600 fax-no: +44 20 33 88 0601 e-mail: tld.ops@centralnic.com nserver: A.NIC.BUILD 194.169.218.20 2001:67c:13cc:0:0:0:1:20 nserver: B.NIC.BUILD 185.24.64.20 2a04:2b00:13cc:0:0:0:1:20 nserver: C.NIC.BUILD 212.18.248.20 2a04:2b00:13ee:0:0:0:0:20 nserver: D.NIC.BUILD 212.18.249.20 2a04:2b00:13ff:0:0:0:0:20 ds-rdata: 54832 8 2 8d0f5d4d637295690e42166227e1a5fd97f412e9ebdc1cb30254f7b8f8aa3792 ds-rdata: 30770 8 2 68e3857b46d09fe8c87b6144a5d61f9613440a6407331ac598970c29809b56f7 whois: whois.nic.build status: ACTIVE remarks: Registration information: https://about.build/ created: 2014-01-09 changed: 2021-11-29 source: IANA
The first response from http://www.designity.build, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with designity.build. 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.