nsaneforums.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 63 days left19 years oldTranco #201140
90
nsaneforums.com was registered on 24 Aug 2007 via eNom, LLC and the registry expiry is 24 Aug 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/nsaneforums.com.
nsaneforums.com publishes 2 nameservers. DNSSEC is not signed.
nsaneforums.com has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.4 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 63 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Browser Insights, HSTS, HTTP/3, Stimulus, Swiper, jQuery and jQuery CDN. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for nsaneforums.com in the checks that ran.
Domain · RDAP/WHOIS
nsaneforums.com was registered on 24 Aug 2007 via eNom, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/nsaneforums.com.
| Registered | since 24 Aug 2007 |
|---|---|
| Created | 24 August 2007 |
| Updated | 20 August 2022 |
| Expires | 24 August 2028 |
| Registrar | eNom, LLC |
| Status | client transfer prohibited |
| Nameservers | dion.ns.cloudflare.com, tia.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/nsaneforums.com |
nsaneforums.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 dion.ns.cloudflare.com is published for nsaneforums.com in the registration record from https://rdap.verisign.com/com/v1/domain/nsaneforums.com.
Nameserver tia.ns.cloudflare.com is published for nsaneforums.com in the registration record from https://rdap.verisign.com/com/v1/domain/nsaneforums.com.
DNS
nsaneforums.com has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.4, 188.114.97.4 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | dion.ns.cloudflare.com, tia.ns.cloudflare.com |
| MX | route2.mx.cloudflare.net (27), route1.mx.cloudflare.net (60), route3.mx.cloudflare.net (93) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at nsaneforums.com is "v=spf1 ip4:176.223.140.18 ip6:2a02:7b40:b0df:8c12::1 include:_spf.mx.cloudflare.net ~all".
The DMARC text record at _dmarc.nsaneforums.com is "v=DMARC1; p=reject; ruf=mailto:[email protected]; adkim=s; aspf=s; pct=40; rua=mailto:[email protected],mailto:[email protected]…".
IPv4 address 188.114.96.4 answers for nsaneforums.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for nsaneforums.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for nsaneforums.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for nsaneforums.com at resolver 1.1.1.1:53.
Mail exchanger route2.mx.cloudflare.net has preference 27.
Mail exchanger route1.mx.cloudflare.net has preference 60.
Mail exchanger route3.mx.cloudflare.net has preference 93.
Hosting and geo
nsaneforums.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.4 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for nsaneforums.com is valid, with 63 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | nsaneforums.com |
| 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: *.nsaneforums.com, nsaneforums.com.
Tech stack
Tech detection checked the fetched homepage and named 8 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- HSTS · Security
- HTTP/3 · Miscellaneous
- Stimulus · JavaScript frameworks
- Swiper · JavaScript libraries
- jQuery · JavaScript libraries
- jQuery CDN · CDN
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Stimulus is filed under JavaScript frameworks.
Swiper is filed under JavaScript libraries.
jQuery is filed under JavaScript libraries.
jQuery CDN is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 201 ms. The target title is 144 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 201 ms |
| Title length | 144 no |
| Quoted title | "Nsane Forums - Computer and Technology Community, Software Update, Free Giveaways, Nsane.Down, Technology Consultations and News, and much more." |
| Meta description | "Nsane Forums is an advanced computer and technology community where you can discover the most up-to-date software, free giveaways, the nsane.down frontpage, technology consultations and news, and much more." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | sameorigin |
| Robots meta | — |
| Canonical | https://nsaneforums.com |
| Language | en-US |
| Links | 213 |
| Images | 41 |
| Favicon | yes |
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 nsaneforums.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 | yes |
| CSP | yes |
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 15 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: dns a changed from 188.114.96.3,188.114.97.3 to 188.114.96.4,188.114.97.4.
Questions
Is nsaneforums.com 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 nsaneforums.com?
nsaneforums.com is placed in Toronto, Canada.
When does nsaneforums.com expire?
nsaneforums.com expires on 24 August 2028 according to https://rdap.verisign.com/com/v1/domain/nsaneforums.com.
Who owns nsaneforums.com?
The registry did not return a person or a company for nsaneforums.com. RDAP often redacts the registrant. The registrar on file is eNom, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/nsaneforums.com at 2026-10-30T14:07:10Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:07:10Z
- TLS source tls:443 at 2026-10-30T14:07:10Z
- HTTP source https://nsaneforums.com/ at 2026-10-30T14:07:10Z
- Tech source wappalyzergo at 2026-10-30T14:07:10Z
- Geo source db-ip at 2026-10-30T14:07:10Z
- Safety source family DNS and local lists at 2026-10-30T14:07:10Z
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.