forowarez.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 63 days left8 years old
60
forowarez.net was registered on 9 Dec 2017 via Internet Domain Service BS Corp and the registry expiry is 9 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/forowarez.net.
forowarez.net publishes 2 nameservers. DNSSEC is not signed.
forowarez.net has 1 IPv4 address (185.53.179.113). The geolocation database places 185.53.179.113 in Munich (Altstadt-Lehel), Germany.
The TLS certificate from YE2 is valid and has 63 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Caddy and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
forowarez.net was registered on 9 Dec 2017 via Internet Domain Service BS Corp. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/forowarez.net.
| Registered | since 9 Dec 2017 |
|---|---|
| Created | 9 December 2017 |
| Updated | 7 December 2025 |
| Expires | 9 December 2026 |
| Registrar | Internet Domain Service BS Corp |
| Status | client transfer prohibited |
| Nameservers | ns1.ibspark.com, ns2.ibspark.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/forowarez.net |
forowarez.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 ns1.ibspark.com is published for forowarez.net in the registration record from https://rdap.verisign.com/net/v1/domain/forowarez.net.
Nameserver ns2.ibspark.com is published for forowarez.net in the registration record from https://rdap.verisign.com/net/v1/domain/forowarez.net.
DNS
forowarez.net has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 185.53.179.113 |
|---|---|
| AAAA | — |
| NS | ns1.ibspark.com, ns2.ibspark.com |
| MX | — |
| SPF | present |
| DMARC | absent |
| CAA | issue letsencrypt.org |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at forowarez.net is "v=spf1 -all".
IPv4 address 185.53.179.113 answers for forowarez.net at resolver 1.1.1.1:53.
A random label under forowarez.net also resolved, which means wildcard DNS is on.
Hosting and geo
forowarez.net is placed in Munich (Altstadt-Lehel), Germany by the local geolocation database (db-ip).
| Address | 185.53.179.113 |
|---|---|
| Country | Germany |
| City | Munich (Altstadt-Lehel) |
| Source | db-ip |
SSL/TLS
The certificate for forowarez.net is valid, with 63 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | forowarez.net |
| Valid from | 4 October 2026 |
| Valid until | 2 January 2027 |
| Days left | 63 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.forowarez.net, forowarez.net.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Caddy · Web servers
- HTTP/3 · Miscellaneous
Caddy is filed under Web servers.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 127 ms. The target title is 13 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 127 ms |
| Title length | 13 yes |
| Quoted title | "forowarez.net" |
| Meta description | "Die besten Informationen und wichtigsten Links zu allen Themen im Zusammenhang mit forowarez.net. This domain is expired. If you are the domain owner please click here to renew it." yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | german |
| 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 forowarez.net is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for forowarez.net. That resolver covers adult and malware names.
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 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 10 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 0 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 Munich (Altstadt-Lehel).
- October 2026: geo country changed from empty to Germany.
Questions
Is forowarez.net safe?
Cloudflare family DNS returned a block for forowarez.net. That resolver covers adult and malware names.
Who hosts forowarez.net?
forowarez.net is placed in Munich (Altstadt-Lehel), Germany.
When does forowarez.net expire?
forowarez.net expires on 9 December 2026 according to https://rdap.verisign.com/net/v1/domain/forowarez.net.
Who owns forowarez.net?
The registry did not return a person or a company for forowarez.net. RDAP often redacts the registrant. The registrar on file is Internet Domain Service BS Corp.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/forowarez.net at 2026-10-30T14:52:03Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:52:03Z
- TLS source tls:443 at 2026-10-30T14:52:03Z
- HTTP source https://forowarez.net/ at 2026-10-30T14:52:03Z
- Tech source wappalyzergo at 2026-10-30T14:52:03Z
- Geo source db-ip at 2026-10-30T14:52:03Z
- Safety source family DNS and local lists at 2026-10-30T14:52:03Z
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.