domain/witolszewski.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 archivewitolszewski.com was registered in December 2025 with OwnRegistrar, and is due to expire in December 2026. Its website was online at the last check, served from GNET Internet Telekomunikasyon A.S.'s network. Email for witolszewski.com is handled by witolszewski.com.
Based on what we observed, its registration expires in 18 days.
| Type | Value |
|---|---|
| A | 104.247.162.226 AS42846 · GNET Internet Telekomunikasyon A.S. · TR |
| MX | 10 mail.witolszewski.com |
| NS | ns31.guzelhosting.com |
| NS | ns32.guzelhosting.com |
| NS | ns33.guzelhosting.com |
| NS | ns34.guzelhosting.com |
| TXT | v=spf1 a mx include:relay.guzelhosting.com ~all |
| SOA | ns31.guzelhosting.com hostmaster.witolszewski.com 2026100103 |
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. witolszewski.com is registered through OwnRegistrar.
witolszewski.com was registered on 9 Dec 2025, making it 11 months old.
The registry lists 9 Dec 2026 as the expiry date, 18 days from now. Most domains renew automatically before then.
witolszewski.com's website is served from GNET Internet Telekomunikasyon A.S.'s network.
Email for witolszewski.com is handled by witolszewski.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.