domain/tessera.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 archivetessera.ai was registered in September 2021 with GoDaddy.com, and is due to expire in September 2029. Its website was online at the last check, served from Amazon.com's network. Email for tessera.ai is handled by messagingengine.com. The website presents it as Tessera (audience intelligence platform).
Registered 5 years ago. The website responds, SPF and DMARC are published and the certificate is trusted.
| Type | Value |
|---|---|
| A | 15.197.225.128 AS16509 · Amazon.com, Inc. · US |
| A | 3.33.251.168 AS16509 · Amazon.com, Inc. · US |
| MX | 10 in1-smtp.messagingengine.com |
| MX | 20 in2-smtp.messagingengine.com |
| NS | ns37.domaincontrol.com |
| NS | ns38.domaincontrol.com |
| TXT | v=spf1 include:spf.messagingengine.com -all |
| DMARC | v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:[email protected]; |
| SOA | ns37.domaincontrol.com dns.jomax.net 2026102101 |
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.
Read from the homepage's code and server headers. Sites can hide what they use, so this list may be incomplete.
Most registries now keep the registrant's details private, and whois.is doesn't show them. tessera.ai is registered through GoDaddy.com. The website presents itself as Tessera; that is the site's own claim, not a verified owner.
tessera.ai was registered on 18 Sept 2021, making it 5 years old.
The registry lists 18 Sept 2029 as the expiry date, 1033 days from now. Most domains renew automatically before then.
tessera.ai's website is served from Amazon.com's network.
Email for tessera.ai is handled by messagingengine.com, according to its MX records.
It was up when we last checked, 19 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.