domain/w398.net
- 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 archivew398.net was registered in February 2010 with OwnRegistrar, and is due to expire in February 2027. Its website was online at the last check, served from netcup's network. Email for w398.net is handled by w398.com. The website presents it as W398 (business solutions and it consulting).
Registered 17 years ago. The website responds, SPF is published, though DMARC is not and the certificate is trusted.
| Type | Value |
|---|---|
| A | 202.61.251.221 AS197540 · netcup GmbH · AT |
| MX | 10 mx.w398.com |
| NS | ns1.w398.net |
| NS | ns2.w398.net |
| NS | ns3.w398.net |
| TXT | v=spf1 a mx ip6:2a03:4000:54:c46::1 -all |
| CAA | 128 issue "letsencrypt.org" |
| SOA | ns1.w398.net domain.vibromax.net 2026030801 |
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. w398.net is registered through OwnRegistrar. The website presents itself as W398; that is the site's own claim, not a verified owner.
w398.net was registered on 19 Feb 2010, making it 16 years old.
The registry lists 19 Feb 2027 as the expiry date, 90 days from now. Most domains renew automatically before then.
w398.net's website is served from netcup's network.
Email for w398.net is handled by w398.com, according to its MX records.
It was up when we last checked, 55 min ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.