domain/circularsna.ke
- 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 archivecircularsna.ke was registered in October 2026 with Truehost AI, and is due to expire in October 2027. Its website was online at the last check, served from Google's network. circularsna.ke doesn't receive email: it publishes no mail servers. The website names Circular Snake as the business behind it.
Based on what we observed, it was registered within the last year and it publishes no email authentication records.
| Type | Value |
|---|---|
| A | 34.111.179.208 AS396982 · Google LLC · US |
| NS | etta.ns.cloudflare.com |
| NS | konnor.ns.cloudflare.com |
| TXT | replit-verify=cb7b8ef7-7dc2-452f-a3da-5d132a19419a |
| SOA | etta.ns.cloudflare.com dns.cloudflare.com 2419222768 |
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 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. circularsna.ke is registered through Truehost AI. The website presents itself as Circular Snake; that is the site's own claim, not a verified owner.
circularsna.ke was registered on 25 Oct 2026, making it 27 days old.
The registry lists 25 Oct 2027 as the expiry date, 338 days from now. Most domains renew automatically before then.
circularsna.ke's website is served from Google's network.
No one: circularsna.ke publishes no MX records, so it can't receive email.
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.