rulesforuse.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 129 days left27 years oldTranco #906806
80
rulesforuse.org was registered on 22 Oct 1999 via Key-Systems GmbH and the registry expiry is 22 Oct 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/rulesforuse.org.
rulesforuse.org publishes 5 nameservers. DNSSEC is not signed.
rulesforuse.org has 1 IPv4 address (80.90.20.101). The geolocation database places 80.90.20.101 in Berlin, Germany.
The TLS certificate from Sectigo Public Server Authentication CA OV E36 is valid and has 129 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Amazon Web Services and HSTS. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for rulesforuse.org in the checks that ran.
Domain · RDAP/WHOIS
rulesforuse.org was registered on 22 Oct 1999 via Key-Systems GmbH. The registry returned 2 status values and 5 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/rulesforuse.org.
| Registered | since 22 Oct 1999 |
|---|---|
| Created | 22 October 1999 |
| Updated | 25 September 2026 |
| Expires | 22 October 2027 |
| Registrar | Key-Systems GmbH |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | ns1.brandshelter.com, ns2.brandshelter.de, ns3.brandshelter.info, ns4.brandshelter.net, ns5.brandshelter.us |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/rulesforuse.org |
rulesforuse.org carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
rulesforuse.org 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.brandshelter.com is published for rulesforuse.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/rulesforuse.org.
Nameserver ns2.brandshelter.de is published for rulesforuse.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/rulesforuse.org.
Nameserver ns3.brandshelter.info is published for rulesforuse.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/rulesforuse.org.
Nameserver ns4.brandshelter.net is published for rulesforuse.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/rulesforuse.org.
Nameserver ns5.brandshelter.us is published for rulesforuse.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/rulesforuse.org.
DNS
rulesforuse.org has 1 address record, 1 mail exchanger and 5 nameservers, measured at 1.1.1.1:53.
| A | 80.90.20.101 |
|---|---|
| AAAA | — |
| NS | ns1.brandshelter.com, ns2.brandshelter.de, ns3.brandshelter.info, ns4.brandshelter.net, ns5.brandshelter.us |
| MX | rulesforuse-org.mail.protection.outlook.com (0) Microsoft 365 |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at rulesforuse.org is "v=spf1 include:spf.protection.outlook.com -all".
The DMARC text record at _dmarc.rulesforuse.org is "v=DMARC1; p=reject; rua=mailto:[email protected]".
IPv4 address 80.90.20.101 answers for rulesforuse.org at resolver 1.1.1.1:53.
Mail exchanger rulesforuse-org.mail.protection.outlook.com has preference 0. The host is recognised as Microsoft 365.
Hosting and geo
rulesforuse.org is placed in Berlin, Germany by the local geolocation database (db-ip).
| Address | 80.90.20.101 |
|---|---|
| Country | Germany |
| City | Berlin |
| Source | db-ip |
SSL/TLS
The certificate for rulesforuse.org is valid, with 129 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Sectigo Public Server Authentication CA OV E36 |
|---|---|
| Subject | rulesforuse.org |
| Valid from | 23 August 2026 |
| Valid until | 9 March 2027 |
| Days left | 129 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: rulesforuse.org, www.rulesforuse.org.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Amazon Web Services · PaaS
- HSTS · Security
Amazon Web Services is filed under PaaS.
HSTS is filed under Security.
On-page checks
The homepage returned HTTP 200 in 23 ms. The target title is 41 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 23 ms |
| Title length | 41 yes |
| Quoted title | "Central Bank Counterfeit Deterrence Group" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | dir= |
| Links | 25 |
| Images | 2 |
| 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 rulesforuse.org 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 | yes |
| 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 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 5 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 Berlin.
- October 2026: geo country changed from empty to Germany.
Questions
Is rulesforuse.org 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 rulesforuse.org?
rulesforuse.org is placed in Berlin, Germany.
When does rulesforuse.org expire?
rulesforuse.org expires on 22 October 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/rulesforuse.org.
Who owns rulesforuse.org?
The registry did not return a person or a company for rulesforuse.org. RDAP often redacts the registrant. The registrar on file is Key-Systems GmbH.
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/rulesforuse.org at 2026-10-30T15:03:22Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:03:22Z
- TLS source tls:443 at 2026-10-30T15:03:22Z
- HTTP source https://rulesforuse.org/ at 2026-10-30T15:03:22Z
- Tech source wappalyzergo at 2026-10-30T15:03:22Z
- Geo source db-ip at 2026-10-30T15:03:22Z
- Safety source family DNS and local lists at 2026-10-30T15:03:22Z
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.