domain/mavenslists.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 archivemavenslists.com was registered in March 2025 with Cosmotown, and is due to expire in March 2027. Its website was online at the last check, served from TierPoint's network. Email for mavenslists.com is handled by mavenslists.com. The website names Mavens Lists as the business behind it.
Registered 2 years ago. The website responds, SPF is published, though DMARC is not and the certificate is trusted.
| Type | Value |
|---|---|
| A | 174.136.29.202 AS17378 · TierPoint, LLC · US |
| MX | 0 mail.mavenslists.com |
| NS | ns1.cloud-e66238.managed-vps.net |
| NS | ns2.cloud-e66238.managed-vps.net |
| TXT | v=spf1 +a +mx +ip4:174.136.29.202 -all |
| SOA | ns1.cloud-e66238.managed-vps.net admin.mavenslists.com 2017111401 |
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. mavenslists.com is registered through Cosmotown. The website presents itself as Mavens Lists; that is the site's own claim, not a verified owner.
mavenslists.com was registered on 19 Mar 2025, making it 1 year old.
The registry lists 19 Mar 2027 as the expiry date, 118 days from now. Most domains renew automatically before then.
mavenslists.com's website is served from TierPoint's network.
Email for mavenslists.com is handled by mavenslists.com, according to its MX records.
It was up when we last checked, 1 day ago (20 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.