domain/edoras.ai
- 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 archiveedoras.ai was registered in July 2025 with GoDaddy.com, and is due to expire in July 2027. Its website was online at the last check, served from Amazon.com's network. edoras.ai doesn't receive email: it publishes no mail servers. The website names edoras.ai as the business behind it.
Registered 1 year ago. The website responds, DMARC is published, though SPF is not and the certificate is trusted.
| Type | Value |
|---|---|
| A | 13.248.243.5 AS16509 · Amazon.com, Inc. · US |
| A | 76.223.105.230 AS16509 · Amazon.com, Inc. · US |
| NS | ns15.domaincontrol.com |
| NS | ns16.domaincontrol.com |
| DMARC | v=DMARC1; p=reject; adkim=r; aspf=r; rua=mailto:[email protected]; |
| SOA | ns15.domaincontrol.com dns.jomax.net 2025072401 |
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.
None stated on the pages we read.
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. edoras.ai is registered through GoDaddy.com. The website presents itself as edoras.ai; that is the site's own claim, not a verified owner.
edoras.ai was registered on 24 Jul 2025, making it 1 year old.
The registry lists 24 Jul 2027 as the expiry date, 246 days from now. Most domains renew automatically before then.
edoras.ai's website is served from Amazon.com's network.
No one: edoras.ai publishes no MX records, so it can't receive email.
It was up when we last checked, 11 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.