publicsex.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blocked27 years old
20
publicsex.com was registered on 2 Sep 1999 via NetTuner Corp. dba Webmasters.com and the registry expiry is 2 Sep 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/publicsex.com.
publicsex.com has 1 IPv4 address (51.81.90.52). The geolocation database places 51.81.90.52 in Irving, United States.
Domain · RDAP/WHOIS
publicsex.com was registered on 2 Sep 1999 via NetTuner Corp. dba Webmasters.com. The registry returned 3 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/publicsex.com.
| Registered | since 2 Sep 1999 |
|---|---|
| Created | 2 September 1999 |
| Updated | 3 September 2026 |
| Expires | 2 September 2027 |
| Registrar | NetTuner Corp. dba Webmasters.com |
| Status | client delete prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns73.webmasters.com, ns74.webmasters.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/publicsex.com |
publicsex.com 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.
publicsex.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.
publicsex.com 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 ns73.webmasters.com is published for publicsex.com in the registration record from https://rdap.verisign.com/com/v1/domain/publicsex.com.
Nameserver ns74.webmasters.com is published for publicsex.com in the registration record from https://rdap.verisign.com/com/v1/domain/publicsex.com.
DNS
publicsex.com has 1 address record, 1 mail exchanger and 0 nameservers, measured at 1.1.1.1:53.
| A | 51.81.90.52 |
|---|---|
| AAAA | — |
| NS | — |
| MX | mail.yaxmail.net (1) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at publicsex.com is "v=spf1 ip6:fdfe:2ac3:1b3b::/48 -all".
IPv4 address 51.81.90.52 answers for publicsex.com at resolver 1.1.1.1:53.
Mail exchanger mail.yaxmail.net has preference 1.
A random label under publicsex.com also resolved, which means wildcard DNS is on.
Hosting and geo
publicsex.com is placed in Irving, United States by the local geolocation database (db-ip).
| Address | 51.81.90.52 |
|---|---|
| Country | United States |
| City | Irving |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for publicsex.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup publicsex.com: 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 publicsex.com 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 publicsex.com. 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 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 5 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: dns a changed from 209.216.87.66 to 51.81.90.52.
- October 2026: geo city changed from empty to Irving.
- October 2026: geo country changed from empty to United States.
Questions
Is publicsex.com safe?
Cloudflare family DNS returned a block for publicsex.com. That resolver covers adult and malware names.
Who hosts publicsex.com?
publicsex.com is placed in Irving, United States.
When does publicsex.com expire?
publicsex.com expires on 2 September 2027 according to https://rdap.verisign.com/com/v1/domain/publicsex.com.
Who owns publicsex.com?
The registry did not return a person or a company for publicsex.com. RDAP often redacts the registrant. The registrar on file is NetTuner Corp. dba Webmasters.com.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/publicsex.com at 2026-10-30T14:10:51Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:10:51Z
- TLS source tls:443 at 2026-10-30T14:10:51Z
- HTTP source https://publicsex.com/ at 2026-10-30T14:10:51Z
- Tech source not available at 2026-10-30T14:10:51Z
- Geo source db-ip at 2026-10-30T14:10:51Z
- Safety source family DNS and local lists at 2026-10-30T14:10:51Z
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.