pornez.co
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 51 days leftUnder 1 year old
22
pornez.co was registered on 15 May 2026 via Dynadot Inc and the registry expiry is 15 May 2027. WHOIS data came from RDAP at https://rdap.registry.co/co/domain/pornez.co.
pornez.co publishes 2 nameservers. DNSSEC is not signed.
pornez.co has 1 IPv4 address (162.4.84.241). The geolocation database places 162.4.84.241 in Los Angeles, United States.
The TLS certificate from YE2 is not valid (TLS 1.3).
Domain · RDAP/WHOIS
pornez.co was registered on 15 May 2026 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.registry.co/co/domain/pornez.co.
| Registered | since 15 May 2026 |
|---|---|
| Created | 15 May 2026 |
| Updated | 12 June 2026 |
| Expires | 15 May 2027 |
| Registrar | Dynadot Inc |
| Status | active |
| Nameservers | ns1.oh313.parklogic.com, ns2.oh313.parklogic.com |
| DNSSEC | no |
| Source | https://rdap.registry.co/co/domain/pornez.co |
Nameserver ns1.oh313.parklogic.com is published for pornez.co in the registration record from https://rdap.registry.co/co/domain/pornez.co.
Nameserver ns2.oh313.parklogic.com is published for pornez.co in the registration record from https://rdap.registry.co/co/domain/pornez.co.
DNS
pornez.co has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 162.4.84.241 |
|---|---|
| AAAA | — |
| NS | ns1.oh313.parklogic.com, ns2.oh313.parklogic.com |
| MX | mx156.hostedmxserver.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | issue letsencrypt.org |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at pornez.co is "v=spf1 -all".
IPv4 address 162.4.84.241 answers for pornez.co at resolver 1.1.1.1:53.
Mail exchanger mx156.hostedmxserver.com has preference 10.
A random label under pornez.co also resolved, which means wildcard DNS is on.
A nameserver belongs to a parking host.
Hosting and geo
pornez.co is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 162.4.84.241 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
SSL/TLS
The certificate for pornez.co is not valid, with 51 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | pornez.co |
| Valid from | 22 September 2026 |
| Valid until | 21 December 2026 |
| Days left | 51 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: pornez.co.
Validation result: certificate did not validate
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 |
|---|
Get "https://pornez.co/": tls: failed to verify certificate: x509: certificate signed by unknown authority
Security
Family DNS for pornez.co 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 pornez.co. 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 10 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 2 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: rdap created changed from empty to 2026-05-15T18:41:05.0Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from empty to 2027-05-15T23:59:59.0Z.
- October 2026: rdap nameservers changed from empty to ns1.oh313.parklogic.com,ns2.oh313.parklogic.com.
- October 2026: rdap registered changed from unknown to yes.
- October 2026: rdap registrar changed from empty to Dynadot Inc.
- October 2026: rdap statuses changed from empty to active.
- October 2026: rdap updated changed from empty to 2026-06-12T20:56:39.0Z.
- October 2026: geo city changed from empty to Los Angeles.
- October 2026: geo country changed from empty to United States.
Questions
Is pornez.co safe?
Cloudflare family DNS returned a block for pornez.co. That resolver covers adult and malware names.
Who hosts pornez.co?
pornez.co is placed in Los Angeles, United States.
When does pornez.co expire?
pornez.co expires on 15 May 2027 according to https://rdap.registry.co/co/domain/pornez.co.
Who owns pornez.co?
The registry did not return a person or a company for pornez.co. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://rdap.registry.co/co/domain/pornez.co at 2026-10-30T13:39:21Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:39:21Z
- TLS source tls:443 at 2026-10-30T13:39:21Z
- HTTP source https://pornez.co/ at 2026-10-30T13:39:21Z
- Tech source not available at 2026-10-30T13:39:21Z
- Geo source db-ip at 2026-10-30T13:39:21Z
- Safety source family DNS and local lists at 2026-10-30T13:39:21Z
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.