femdom-pov.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 76 days left12 years old
35
femdom-pov.net was registered on 5 Feb 2014 via PDR Ltd. d/b/a PublicDomainRegistry.com and the registry expiry is 5 Feb 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/femdom-pov.net.
femdom-pov.net publishes 2 nameservers. DNSSEC is not signed.
femdom-pov.net has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.4 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 76 days left (TLS 1.3).
Domain · RDAP/WHOIS
femdom-pov.net was registered on 5 Feb 2014 via PDR Ltd. d/b/a PublicDomainRegistry.com. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/femdom-pov.net.
| Registered | since 5 Feb 2014 |
|---|---|
| Created | 5 February 2014 |
| Updated | 2 July 2025 |
| Expires | 5 February 2027 |
| Registrar | PDR Ltd. d/b/a PublicDomainRegistry.com |
| Status | client transfer prohibited |
| Nameservers | bill.ns.cloudflare.com, nia.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/femdom-pov.net |
femdom-pov.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 bill.ns.cloudflare.com is published for femdom-pov.net in the registration record from https://rdap.verisign.com/net/v1/domain/femdom-pov.net.
Nameserver nia.ns.cloudflare.com is published for femdom-pov.net in the registration record from https://rdap.verisign.com/net/v1/domain/femdom-pov.net.
DNS
femdom-pov.net has 4 address records, 0 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::4, 2a06:98c1:3121::4 |
| NS | bill.ns.cloudflare.com, nia.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.4 answers for femdom-pov.net at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for femdom-pov.net at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::4 answers for femdom-pov.net at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::4 answers for femdom-pov.net at resolver 1.1.1.1:53.
Hosting and geo
femdom-pov.net 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 femdom-pov.net is valid, with 76 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | femdom-pov.net |
| Valid from | 17 October 2026 |
| Valid until | 15 January 2027 |
| Days left | 76 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.femdom-pov.net, femdom-pov.net.
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://femdom-pov.me/": context deadline exceeded
Security
Family DNS for femdom-pov.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 | no |
Cloudflare family DNS returned a block for femdom-pov.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.
Score breakdown
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 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 188.114.96.3,188.114.97.3 to 188.114.96.4,188.114.97.4.
- October 2026: dns aaaa changed from 2a06:98c1:3120::3,2a06:98c1:3121::3 to 2a06:98c1:3120::4,2a06:98c1:3121::4.
- October 2026: http hsts changed from true to false.
- October 2026: http status_class changed from 2xx to empty.
- October 2026: tech removed Cloudflare.
- October 2026: tech removed HSTS.
- October 2026: tech removed HTTP/3.
- October 2026: tech removed MySQL.
- October 2026: tech removed OWL Carousel.
- October 2026: tech removed PHP.
- October 2026: tech removed WordPress.
- October 2026: tech removed WordPress Default.
- October 2026: tech removed WordPress Super Cache.
- October 2026: tech removed jQuery.
Questions
Is femdom-pov.net safe?
Cloudflare family DNS returned a block for femdom-pov.net. That resolver covers adult and malware names.
Who hosts femdom-pov.net?
femdom-pov.net is placed in Toronto, Canada.
When does femdom-pov.net expire?
femdom-pov.net expires on 5 February 2027 according to https://rdap.verisign.com/net/v1/domain/femdom-pov.net.
Who owns femdom-pov.net?
The registry did not return a person or a company for femdom-pov.net. RDAP often redacts the registrant. The registrar on file is PDR Ltd. d/b/a PublicDomainRegistry.com.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/femdom-pov.net at 2026-10-30T14:52:02Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:52:02Z
- TLS source tls:443 at 2026-10-30T14:52:02Z
- HTTP source https://femdom-pov.net/ at 2026-10-30T14:52:02Z
- Tech source not available at 2026-10-30T14:52:02Z
- Geo source db-ip at 2026-10-30T14:52:02Z
- Safety source family DNS and local lists at 2026-10-30T14:52:02Z
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.