domain/aminidigital.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 archiveaminidigital.com was registered in January 2024 with Registrar.eu, and is due to expire in January 2030. Its website was online at the last check, served from OVH's network. Email for aminidigital.com is handled by aminidigital.com.
Registered 3 years ago. The website responds, SPF and DMARC are published and the certificate is trusted.
| Type | Value |
|---|---|
| A | 178.32.103.89 AS16276 · OVH SAS · FR |
| MX | 0 aminidigital.com |
| NS | ns1.cloudoon.com |
| NS | ns2.cloudoon.net |
| NS | ns3.cloudoon.org |
| TXT | v=spf1 +a +mx include:_spf.truehostcloud.com ~all |
| DMARC | v=DMARC1;p=quarantine;sp=quarantine;adkim=r;aspf=s;pct=100;fo=0;rf=afrf;ri=86400;rua=mailto:[email protected];ruf=mailto:[email protected] |
| SOA | ns1.cloudoon.com root.rbx111.truehost.cloud 2026101001 |
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. aminidigital.com is registered through Registrar.eu.
aminidigital.com was registered on 31 Jan 2024, making it 2 years old.
The registry lists 31 Jan 2030 as the expiry date, 1168 days from now. Most domains renew automatically before then.
aminidigital.com's website is served from OVH's network.
Email for aminidigital.com is handled by aminidigital.com, according to its MX records.
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.