wellez.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403SafeSSL: 135 days left21 years old
50
wellez.net was registered on 10 Apr 2005 via Network Solutions, LLC and the registry expiry is 10 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/wellez.net.
wellez.net publishes 2 nameservers. DNSSEC is not signed.
wellez.net has 1 IPv4 address (52.171.136.200). The geolocation database places 52.171.136.200 in San Antonio, United States.
The TLS certificate from Go Daddy Secure Certificate Authority - G2 is valid and has 135 days left (TLS 1.3).
No safety warning was recorded for wellez.net in the checks that ran.
Domain · RDAP/WHOIS
wellez.net was registered on 10 Apr 2005 via Network Solutions, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/wellez.net.
| Registered | since 10 Apr 2005 |
|---|---|
| Created | 10 April 2005 |
| Updated | 9 February 2026 |
| Expires | 10 April 2027 |
| Registrar | Network Solutions, LLC |
| Status | client transfer prohibited |
| Nameservers | a1.uberns.com, b1.uberns.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/wellez.net |
wellez.net carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver a1.uberns.com is published for wellez.net in the registration record from https://rdap.verisign.com/net/v1/domain/wellez.net.
Nameserver b1.uberns.com is published for wellez.net in the registration record from https://rdap.verisign.com/net/v1/domain/wellez.net.
DNS
wellez.net has 1 address record, 6 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 52.171.136.200 |
|---|---|
| AAAA | — |
| NS | a1.uberns.com, b1.uberns.com |
| MX | mailserver.wellez.net (0), mail.wellez.net (5), mail1.wellez.net (6), mx2.wellez.net (6), rsmailserver.wellez.net (8), mail2.wellez.net (10) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 52.171.136.200 answers for wellez.net at resolver 1.1.1.1:53.
Mail exchanger mailserver.wellez.net has preference 0.
Mail exchanger mail.wellez.net has preference 5.
Mail exchanger mail1.wellez.net has preference 6.
Mail exchanger mx2.wellez.net has preference 6.
Mail exchanger rsmailserver.wellez.net has preference 8.
Mail exchanger mail2.wellez.net has preference 10.
A random label under wellez.net also resolved, which means wildcard DNS is on.
Hosting and geo
wellez.net is placed in San Antonio, United States by the local geolocation database (db-ip).
| Address | 52.171.136.200 |
|---|---|
| Country | United States |
| City | San Antonio |
| Source | db-ip |
SSL/TLS
The certificate for wellez.net is valid, with 135 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Go Daddy Secure Certificate Authority - G2 |
|---|---|
| Subject | *.wellez.net |
| Valid from | 19 February 2026 |
| Valid until | 15 March 2027 |
| Days left | 135 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.wellez.net, wellez.net.
Tech stack
Tech detection checked the fetched homepage and named 0 products. Source: wappalyzergo.
The fingerprint set matched no product. That is a result, not a skipped check.
On-page checks
The homepage returned HTTP 403 in 385 ms. The target title is 21 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 385 ms |
| Title length | 21 yes |
| Quoted title | "Web App - Unavailable" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for wellez.net is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to San Antonio.
- October 2026: geo country changed from empty to United States.
Questions
Is wellez.net safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts wellez.net?
wellez.net is placed in San Antonio, United States.
When does wellez.net expire?
wellez.net expires on 10 April 2027 according to https://rdap.verisign.com/net/v1/domain/wellez.net.
Who owns wellez.net?
The registry did not return a person or a company for wellez.net. RDAP often redacts the registrant. The registrar on file is Network Solutions, LLC.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/wellez.net at 2026-10-30T14:56:52Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:56:52Z
- TLS source tls:443 at 2026-10-30T14:56:52Z
- HTTP source https://wellez.net/ at 2026-10-30T14:56:52Z
- Tech source wappalyzergo at 2026-10-30T14:56:52Z
- Geo source db-ip at 2026-10-30T14:56:52Z
- Safety source family DNS and local lists at 2026-10-30T14:56:52Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.