domain/americansif.com
- Registration data
RDAP - DNS records
A, AAAA, MX, NS, TXT, CAA, SOA - Email policy
_dmarc - TLS certificate
port 443 - Website snapshot
HTTP - Comparing with history
whois.is archive
RDAPA, AAAA, MX, NS, TXT, CAA, SOA_dmarcport 443HTTPwhois.is archiveamericansif.com was registered in October 2026 with NameSilo, and is due to expire in October 2027. Its website was online at the last check, served from Amazon.com's network. americansif.com doesn't receive email: it publishes no mail servers. The website presents it as American Super Intelligence Force (SIF) (domain for sale).
Based on what we observed, it was registered within the last year and it publishes no email authentication records.
| Type | Value |
|---|---|
| A | 44.232.173.249 AS16509 · Amazon.com, Inc. · US |
| A | 52.40.42.113 AS16509 · Amazon.com, Inc. · US |
| NS | launch1.spaceship.net |
| NS | launch2.spaceship.net |
| TXT | 8c21cf53-5b94-437b-8083-b785b5c2bef6 |
| SOA | launch1.spaceship.net support.spaceship.com 1791128800 |
A network is whoever runs the servers behind the address. With a CDN such as Cloudflare in front, that is the CDN, not the company hosting the site behind it.
We didn't recognise any technology on the homepage.
No public prices on the pages we read.
Every value is quoted from the page linked beside it. Read from 1 page.
First observation recorded. Every change from here on is preserved and shown here.
Most registries now keep the registrant's details private, and whois.is doesn't show them. americansif.com is registered through NameSilo. The website presents itself as American Super Intelligence Force (SIF); that is the site's own claim, not a verified owner.
americansif.com was registered on 4 Oct 2026, making it 1 month old.
The registry lists 4 Oct 2027 as the expiry date, 317 days from now. Most domains renew automatically before then.
americansif.com's website is served from Amazon.com's network.
No one: americansif.com publishes no MX records, so it can't receive email.
It was up when we last checked, 3 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.