pornbits.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe21 years old
30
pornbits.net was registered on 3 Jan 2005 via Squarespace Domains II LLC and the registry expiry is 3 Jan 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/pornbits.net.
pornbits.net publishes 4 nameservers. DNSSEC is not signed.
pornbits.net has 1 IPv4 address (209.240.109.106). The geolocation database places 209.240.109.106 in New York, United States.
No safety warning was recorded for pornbits.net in the checks that ran.
Domain · RDAP/WHOIS
pornbits.net was registered on 3 Jan 2005 via Squarespace Domains II LLC. The registry returned 2 status values and 4 nameservers from https://rdap.verisign.com/net/v1/domain/pornbits.net.
| Registered | since 3 Jan 2005 |
|---|---|
| Created | 3 January 2005 |
| Updated | 20 December 2025 |
| Expires | 3 January 2027 |
| Registrar | Squarespace Domains II LLC |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/pornbits.net |
pornbits.net 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.
pornbits.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 ns-cloud-a1.googledomains.com is published for pornbits.net in the registration record from https://rdap.verisign.com/net/v1/domain/pornbits.net.
Nameserver ns-cloud-a2.googledomains.com is published for pornbits.net in the registration record from https://rdap.verisign.com/net/v1/domain/pornbits.net.
Nameserver ns-cloud-a3.googledomains.com is published for pornbits.net in the registration record from https://rdap.verisign.com/net/v1/domain/pornbits.net.
Nameserver ns-cloud-a4.googledomains.com is published for pornbits.net in the registration record from https://rdap.verisign.com/net/v1/domain/pornbits.net.
DNS
pornbits.net has 1 address record, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 209.240.109.106 |
|---|---|
| AAAA | — |
| NS | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 209.240.109.106 answers for pornbits.net at resolver 1.1.1.1:53.
Hosting and geo
pornbits.net is placed in New York, United States by the local geolocation database (db-ip).
| Address | 209.240.109.106 |
|---|---|
| Country | United States |
| City | New York |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for pornbits.net on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 209.240.109.106:443: i/o timeout
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Security
Family DNS for pornbits.net 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.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 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 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.
Change history
- October 2026: geo city changed from empty to New York.
- October 2026: geo country changed from empty to United States.
Questions
Is pornbits.net 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 pornbits.net?
pornbits.net is placed in New York, United States.
When does pornbits.net expire?
pornbits.net expires on 3 January 2027 according to https://rdap.verisign.com/net/v1/domain/pornbits.net.
Who owns pornbits.net?
The registry did not return a person or a company for pornbits.net. RDAP often redacts the registrant. The registrar on file is Squarespace Domains II LLC.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/pornbits.net at 2026-10-30T14:55:06Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:55:06Z
- TLS source tls:443 at 2026-10-30T14:55:06Z
- HTTP source https://pornbits.net/ at 2026-10-30T14:55:06Z
- Tech source not available at 2026-10-30T14:55:06Z
- Geo source db-ip at 2026-10-30T14:55:06Z
- Safety source family DNS and local lists at 2026-10-30T14:55:06Z
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.