domain/weeget.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 archiveweeget.com was registered in July 2007 with RegistryGate, and is due to expire in July 2027. Its website was online at the last check, served from Neue Medien Muennich's network. Email for weeget.com is handled by kasserver.com. The website presents it as Weeget Trading Journal (trading journal).
Registered 19 years ago. The website responds, SPF and DMARC are published and the certificate is trusted.
| Type | Value |
|---|---|
| A | 85.13.155.11 AS34788 · Neue Medien Muennich GmbH · DE |
| MX | 10 w01e46bc.kasserver.com |
| NS | ns5.kasserver.com |
| NS | ns6.kasserver.com |
| TXT | v=spf1 a mx include:spf.kasserver.com ~all |
| DMARC | v=DMARC1; p=none; |
| SOA | ns5.kasserver.com hostmaster.kasserver.com 2608090145 |
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. weeget.com is registered through RegistryGate. The website presents itself as Weeget Trading Journal; that is the site's own claim, not a verified owner.
weeget.com was registered on 31 Jul 2007, making it 19 years old.
The registry lists 31 Jul 2027 as the expiry date, 253 days from now. Most domains renew automatically before then.
weeget.com's website is served from Neue Medien Muennich's network.
Email for weeget.com is handled by kasserver.com, according to its MX records.
It was up when we last checked, 2 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.