crowd.aws was registered with whois.nic.aws on 18 Mar 2016. 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 crowd.aws. Refresh the analysis to check again.
2,547 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| crowd.com.bd | Other extension | 8 Nov 2026 | Checking… | Report → |
| crowd.lol | Other extension | 7 Nov 2026 | Checking… | Report → |
| crowd.pics | Other extension | 21 Oct 2026 | Checking… | Report → |
| crowd.football | Other extension | 20 Oct 2026 | Checking… | Report → |
| crowd.ly | Other extension | 6 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is crowd.aws’s name taken on other extensions?
| Host | Name server | TTL |
|---|---|---|
| crowd.aws | ns-1328.awsdns-38.org | 86400 |
| crowd.aws | ns-1719.awsdns-22.co.uk | 86400 |
| crowd.aws | ns-172.awsdns-21.com | 86400 |
| crowd.aws | ns-774.awsdns-32.net | 86400 |
| Host | Text | TTL |
|---|---|---|
| crowd.aws | "v=spf1 -all" | 900 |
| Host | Start of authority | TTL |
|---|---|---|
| crowd.aws | ns-774.awsdns-32.net awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
No reviews yet. Used crowd.aws? 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.
crowd.aws has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
crowd.aws is registered through whois.nic.aws. See WHOIS →
crowd.aws was registered on 18 Mar 2016, making it 10 years old. See Overview →
Raw registry data for crowd.aws. 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.aws domain: AWS organisation: AWS Registry LLC address: 410 Terry Avenue North address: Seattle WA 98109 address: United States of America (the) contact: administrative name: Sr. Manager organisation: AWS Registry LLC address: 410 Terry Avenue North address: Seattle WA 98109 address: United States of America (the) phone: +1-206-765-5360 fax-no: +1-206-946-7702 e-mail: aws-registry@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.AWS 213.248.218.53 2a01:618:402:0:0:0:0:53 nserver: DNS2.NIC.AWS 103.49.82.53 2401:fd80:402:0:0:0:0:53 nserver: DNS3.NIC.AWS 213.248.222.53 2a01:618:406:0:0:0:0:53 nserver: DNS4.NIC.AWS 2401:fd80:406:0:0:0:0:53 43.230.50.53 nserver: DNSA.NIC.AWS 156.154.100.3 2001:502:ad09:0:0:0:0:3 nserver: DNSB.NIC.AWS 156.154.101.3 2001:502:2eda:0:0:0:0:3 nserver: DNSC.NIC.AWS 156.154.102.3 2610:a1:1009:0:0:0:0:3 nserver: DNSD.NIC.AWS 156.154.103.3 2610:a1:1010:0:0:0:0:3 ds-rdata: 54182 8 2 76f2c3fbb9f23ff5f59a4cd63b8d5d5174b3f2e0f034b7323c1543312f37301d whois: whois.nic.aws status: ACTIVE remarks: Registration information: https://www.amazonregistry.com created: 2016-03-18 changed: 2021-11-20 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with crowd.aws. 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.