rapeboard.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
45
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
45
rapeboard.net was registered on 23 Jan 2016 via Tucows Domains Inc. and the registry expiry is 23 Jan 2028. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/rapeboard.net.
rapeboard.net publishes 2 nameservers. DNSSEC is not signed.
rapeboard.net has 2 IPv4 addresses (104.21.37.237, 172.67.215.55) and 2 IPv6 addresses (2606:4700:3034::6815:25ed, 2606:4700:3037::ac43:d737). The geolocation database places 104.21.37.237 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 62 days left (TLS 1.3).
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
rapeboard.net was registered on 23 Jan 2016 via Tucows Domains Inc.. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/net/v1/domain/rapeboard.net.
| Registered | since 23 Jan 2016 |
|---|---|
| Created | 23 January 2016 |
| Updated | 11 March 2026 |
| Expires | 23 January 2028 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | hugh.ns.cloudflare.com, kami.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/rapeboard.net |
rapeboard.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.
rapeboard.net carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver hugh.ns.cloudflare.com is published for rapeboard.net in the registration record from https://rdap.verisign.com/net/v1/domain/rapeboard.net.
Nameserver kami.ns.cloudflare.com is published for rapeboard.net in the registration record from https://rdap.verisign.com/net/v1/domain/rapeboard.net.
rapeboard.net has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.37.237, 172.67.215.55 |
|---|---|
| AAAA | 2606:4700:3034::6815:25ed, 2606:4700:3037::ac43:d737 |
| NS | hugh.ns.cloudflare.com, kami.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.37.237 answers for rapeboard.net at resolver 1.1.1.1:53.
IPv4 address 172.67.215.55 answers for rapeboard.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::6815:25ed answers for rapeboard.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::ac43:d737 answers for rapeboard.net at resolver 1.1.1.1:53.
rapeboard.net is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.37.237 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for rapeboard.net is valid, with 62 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | rapeboard.net |
| Valid from | 3 October 2026 |
| Valid until | 1 January 2027 |
| Days left | 62 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.rapeboard.net, rapeboard.net.
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
The homepage returned HTTP 403 in 26 ms. The target title is 16 characters and the page has 0 H1 headings.
| Status | 403 |
|---|---|
| TTFB | 26 ms |
| Title length | 16 yes |
| Quoted title | "Just a moment..." |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex,nofollow |
| Canonical | — |
| Language | en-US |
| 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.
Family DNS for rapeboard.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 | yes |
Cloudflare family DNS returned a block for rapeboard.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.
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 10 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.
First checked on 30 October 2026; changes will appear here.
Cloudflare family DNS returned a block for rapeboard.net. That resolver covers adult and malware names.
rapeboard.net is placed in Toronto, Canada.
rapeboard.net expires on 23 January 2028 according to https://rdap.verisign.com/net/v1/domain/rapeboard.net.
The registry did not return a person or a company for rapeboard.net. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
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.