domain/aim.top
- 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 archiveaim.top was registered in April 2026 with PDR, and is due to expire in April 2027. Its website was online at the last check, served from Timeweb, LLP's network. Email for aim.top is handled by Google. The website presents it as AIM Agency (ai-powered agency).
Registered 1 year ago. The website responds, SPF is published, though DMARC is not and the certificate is trusted.
| Type | Value |
|---|---|
| A | 185.125.202.161 AS210976 · Timeweb, LLP · RU |
| A | 92.246.76.92 AS9123 · JSC _TIMEWEB_ · AE |
| MX | 1 smtp.google.com |
| NS | ns1.timeweb.ru |
| NS | ns2.timeweb.ru |
| NS | ns3.timeweb.org |
| NS | ns4.timeweb.org |
| TXT | google-site-verification=-TIsU7W8G6E7cAHxKvug8RjUxdjFga9pOAShPXILwBs |
| TXT | v=spf1 include:_spf.timeweb.ru ~all |
| SOA | ns1.timeweb.ru dns.timeweb.ru 24 |
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.
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. aim.top is registered through PDR. The website presents itself as AIM Agency; that is the site's own claim, not a verified owner.
aim.top was registered on 18 Apr 2026, making it 7 months old.
The registry lists 18 Apr 2027 as the expiry date, 148 days from now. Most domains renew automatically before then.
aim.top's website is served from Timeweb, LLP and JSC _TIMEWEB_'s network.
Email for aim.top is handled by Google, 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.