domain/puremental.org
- 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 archivepuremental.org was registered in March 2025 with NameSilo, and is due to expire in March 2027. Its website was online at the last check, served from HOSTKEY's network. Email for puremental.org is handled by puremental.org. The website names Pure Mental as the business behind it.
Registered 2 years ago. The website responds, SPF and DMARC are published and the certificate is trusted.
| Type | Value |
|---|---|
| A | 151.247.219.111 AS57043 · HOSTKEY B.V. · AE |
| MX | 0 puremental.org |
| NS | ns1.uptimeseo.com |
| NS | ns2.uptimeseo.com |
| TXT | v=spf1 a mx ip4:151.247.219.111 ~all |
| DMARC | v=DMARC1; p=none; |
| SOA | ns1.uptimeseo.com admin.uptimeseo.com 2026102303 |
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 2 pages.
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. puremental.org is registered through NameSilo. The website presents itself as Pure Mental; that is the site's own claim, not a verified owner.
puremental.org was registered on 26 Mar 2025, making it 1 year old.
The registry lists 26 Mar 2027 as the expiry date, 125 days from now. Most domains renew automatically before then.
puremental.org's website is served from HOSTKEY's network.
Email for puremental.org is handled by puremental.org, according to its MX records.
It was up when we last checked, 21 hours ago (20 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.