w3booster.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
w3booster.com was registered on 12 Jun 2019 via InterNetX GmbH and the registry expiry is 12 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/w3booster.com.
w3booster.com publishes 4 nameservers. DNSSEC is not signed.
w3booster.com has 1 IPv4 address (85.215.195.86). The geolocation database places 85.215.195.86 in Berlin (Charlottenburg-Wilmersdorf), Germany.
The TLS certificate from YE1 is valid and has 59 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apache HTTP Server. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for w3booster.com in the checks that ran.
w3booster.com was registered on 12 Jun 2019 via InterNetX GmbH. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/w3booster.com.
| Registered | since 12 Jun 2019 |
|---|---|
| Created | 12 June 2019 |
| Updated | 13 June 2026 |
| Expires | 12 June 2027 |
| Registrar | InterNetX GmbH |
| Status | client transfer prohibited |
| Nameservers | a.ns14.net, b.ns14.net, c.ns14.net, d.ns14.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/w3booster.com |
w3booster.com 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 a.ns14.net is published for w3booster.com in the registration record from https://rdap.verisign.com/com/v1/domain/w3booster.com.
Nameserver b.ns14.net is published for w3booster.com in the registration record from https://rdap.verisign.com/com/v1/domain/w3booster.com.
Nameserver c.ns14.net is published for w3booster.com in the registration record from https://rdap.verisign.com/com/v1/domain/w3booster.com.
Nameserver d.ns14.net is published for w3booster.com in the registration record from https://rdap.verisign.com/com/v1/domain/w3booster.com.
w3booster.com has 1 address record, 1 mail exchanger and 4 nameservers, measured at 1.1.1.1:53.
| A | 85.215.195.86 |
|---|---|
| AAAA | — |
| NS | a.ns14.net, b.ns14.net, c.ns14.net, d.ns14.net |
| MX | w3booster-com.mail.protection.outlook.com (0) Microsoft 365 |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at w3booster.com is "v=spf1 include:spf.protection.outlook.com -all".
IPv4 address 85.215.195.86 answers for w3booster.com at resolver 1.1.1.1:53.
Mail exchanger w3booster-com.mail.protection.outlook.com has preference 0. The host is recognised as Microsoft 365.
A random label under w3booster.com also resolved, which means wildcard DNS is on.
w3booster.com is placed in Berlin (Charlottenburg-Wilmersdorf), Germany by the local geolocation database (db-ip).
| Address | 85.215.195.86 |
|---|---|
| Country | Germany |
| City | Berlin (Charlottenburg-Wilmersdorf) |
| Source | db-ip |
The certificate for w3booster.com is valid, with 59 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | w3booster.com |
| Valid from | 1 October 2026 |
| Valid until | 30 December 2026 |
| Days left | 59 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: w3booster.com, www.w3booster.com.
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
Apache HTTP Server is filed under Web servers.
The homepage returned HTTP 200 in 13 ms. The target title is 39 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 13 ms |
| Title length | 39 yes |
| Quoted title | "W3Booster — Your Warcraft III workspace" |
| Meta description | "W3Booster is the Warcraft III workspace for live match apps, stream overlays, in-game tools, and recording." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 31 |
| Images | 11 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for w3booster.com 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.
Availability 25 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 5 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.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
w3booster.com is placed in Berlin (Charlottenburg-Wilmersdorf), Germany.
w3booster.com expires on 12 June 2027 according to https://rdap.verisign.com/com/v1/domain/w3booster.com.
The registry did not return a person or a company for w3booster.com. RDAP often redacts the registrant. The registrar on file is InterNetX GmbH.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.