trustaml.bot was registered on 11 Nov 2015. Its SSL certificate from Google Trust Services expired on 13 Aug 2025.
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.
17 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| trustaml.site | Other extension | 12 Nov 2026 | Checking… | Report → |
| trustaml.app | Other extension | 30 Sept 2026 | Checking… | Report → |
| trustzml.top | Typo | 30 Sept 2026 | Checking… | Report → |
| trustzml.vip | Typo | 30 Sept 2026 | Checking… | Report → |
| trustal.io | Typo | 5 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is trustaml.bot’s name taken on other extensions?
Every IP address trustaml.bot resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| trustaml.bot | 104.21.80.76 | 300 |
| trustaml.bot | 172.67.175.228 | 300 |
| Host | IPv6 address | TTL |
|---|---|---|
| trustaml.bot | 2606:4700:3030::ac43:afe4 | 300 |
| trustaml.bot | 2606:4700:3032::6815:504c | 300 |
| Host | Name server | TTL |
|---|---|---|
| trustaml.bot | chelsea.ns.cloudflare.com | 21600 |
| trustaml.bot | melnicoff.ns.cloudflare.com | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| trustaml.bot | chelsea.ns.cloudflare.com dns.cloudflare.com 2372842672 10000 2400 604800 1800 | 1800 |
Other domains served from 172.67.175.228. Normal for shared hosting and CDNs.
No reviews yet. Used trustaml.bot? 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.
trustaml.bot has no community safety rating yet. Its SSL certificate expired on 13 Aug 2025. See Security →
trustaml.bot was registered on 11 Nov 2015, making it 11 years old. See Overview →
trustaml.bot is served from 2 IP addresses, mainly on AS13335. See Hosting →
Raw registry data for trustaml.bot. 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: BOT organisation: Amazon Registry Services, Inc. address: 410 Terry Avenue North address: Seattle WA 98109 address: United States of America (the) contact: administrative name: Program Manager, Registry organisation: Amazon Registry Services, Inc. address: 410 Terry Avenue North address: Seattle WA 98109 address: United States of America (the) phone: +1 206 646 5990 fax-no: +1 206 946 7702 e-mail: arsi-rzm@amazon.com contact: technical name: TLD Registry Services Technical organisation: Nominet address: Minerva House address: Edmund Halley Road address: Oxford Science Park address: Oxford OX4 4DQ address: United Kingdom of Great Britain and Northern Ireland (the) phone: +44.1865332211 e-mail: registrytechnical@nominet.uk nserver: DNS1.NIC.BOT 213.248.218.55 2a01:618:402:0:0:0:0:55 nserver: DNS2.NIC.BOT 103.49.82.55 2401:fd80:402:0:0:0:0:55 nserver: DNS3.NIC.BOT 213.248.222.55 2a01:618:406:0:0:0:0:55 nserver: DNS4.NIC.BOT 2401:fd80:406:0:0:0:0:55 43.230.50.55 nserver: DNSA.NIC.BOT 156.154.100.3 2001:502:ad09:0:0:0:0:3 nserver: DNSB.NIC.BOT 156.154.101.3 2001:502:2eda:0:0:0:0:3 nserver: DNSC.NIC.BOT 156.154.102.3 2610:a1:1009:0:0:0:0:3 nserver: DNSD.NIC.BOT 156.154.103.3 2610:a1:1010:0:0:0:0:3 ds-rdata: 58741 8 2 eca26804355a4735caa906601c7d388af755ab40f599d02f29d16f347705ee42 whois: status: ACTIVE remarks: Registration information: http://www.nic.bot created: 2015-11-12 changed: 2025-02-14 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with trustaml.bot. 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.