domain/manationtogo.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 archivemanationtogo.com was registered in February 2013 with PublicDomainRegistry.com, and is due to expire in February 2027. Its website was online at the last check, served from O2SWITCH's network. Email for manationtogo.com is handled by manationtogo.com. The website names ManationTogo as the business behind it.
Registered 14 years ago. The website responds, SPF is published, though DMARC is not and the certificate is trusted.
| Type | Value |
|---|---|
| A | 185.154.139.204 AS50474 · O2SWITCH SAS · FR |
| MX | 0 mail.manationtogo.com |
| NS | ns1.o2switch.net |
| NS | ns2.o2switch.net |
| TXT | v=spf1 ip4:109.234.162.103 +a +mx include:spf.jabatus.fr ~all |
| SOA | ns1.o2switch.net support.o2switch.fr 2022120203 |
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.
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 3 pages.
Most registries now keep the registrant's details private, and whois.is doesn't show them. manationtogo.com is registered through PublicDomainRegistry.com. The website presents itself as ManationTogo; that is the site's own claim, not a verified owner.
manationtogo.com was registered on 9 Feb 2013, making it 13 years old.
The registry lists 9 Feb 2027 as the expiry date, 80 days from now. Most domains renew automatically before then.
manationtogo.com's website is served from O2SWITCH's network.
Email for manationtogo.com is handled by manationtogo.com, according to its MX records.
It was up when we last checked, 9 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.