privateiptvaccess.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 46 days left4 years old
80
privateiptvaccess.com was registered on 15 Feb 2022 via Tucows Domains Inc. and the registry expiry is 15 Feb 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/privateiptvaccess.com.
privateiptvaccess.com publishes 2 nameservers. DNSSEC is not signed.
privateiptvaccess.com has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 46 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Browser Insights, HTTP/3 and Unpkg. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for privateiptvaccess.com in the checks that ran.
Domain · RDAP/WHOIS
privateiptvaccess.com was registered on 15 Feb 2022 via Tucows Domains Inc.. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/privateiptvaccess.com.
| Registered | since 15 Feb 2022 |
|---|---|
| Created | 15 February 2022 |
| Updated | 5 October 2026 |
| Expires | 15 February 2028 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | melina.ns.cloudflare.com, vick.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/privateiptvaccess.com |
privateiptvaccess.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.
privateiptvaccess.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 melina.ns.cloudflare.com is published for privateiptvaccess.com in the registration record from https://rdap.verisign.com/com/v1/domain/privateiptvaccess.com.
Nameserver vick.ns.cloudflare.com is published for privateiptvaccess.com in the registration record from https://rdap.verisign.com/com/v1/domain/privateiptvaccess.com.
DNS
privateiptvaccess.com has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | melina.ns.cloudflare.com, vick.ns.cloudflare.com |
| MX | route1.mx.cloudflare.net (40), route2.mx.cloudflare.net (59), 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 privateiptvaccess.com is "v=spf1 include:_spf.mx.cloudflare.net ~all".
The DMARC text record at _dmarc.privateiptvaccess.com is "v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; rf=afrf; pct=100".
IPv4 address 188.114.96.3 answers for privateiptvaccess.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for privateiptvaccess.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for privateiptvaccess.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for privateiptvaccess.com at resolver 1.1.1.1:53.
Mail exchanger route1.mx.cloudflare.net has preference 40.
Mail exchanger route2.mx.cloudflare.net has preference 59.
Mail exchanger route3.mx.cloudflare.net has preference 93.
Hosting and geo
privateiptvaccess.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for privateiptvaccess.com is valid, with 46 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | privateiptvaccess.com |
| Valid from | 18 September 2026 |
| Valid until | 17 December 2026 |
| Days left | 46 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.privateiptvaccess.com, privateiptvaccess.com.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- HTTP/3 · Miscellaneous
- Unpkg · CDN
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
HTTP/3 is filed under Miscellaneous.
Unpkg is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 120 ms. The target title is 72 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 120 ms |
| Title length | 72 no |
| Quoted title | "Private IPTV Access : Reliable & Best IPTV subscription service provider" |
| Meta description | "We are owner IPTV server | Very Stable Streams & Locals | We have more than 38,000 channels and more Than 65,000 VOD and series. 3 Months $25 only with 2 connections. Just Amazing!" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | https://privateiptvaccess.com |
| Language | en |
| Links | 120 |
| Images | 124 |
| 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 privateiptvaccess.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 | 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 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 5 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.4,188.114.97.4 to 188.114.96.3,188.114.97.3.
Questions
Is privateiptvaccess.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 privateiptvaccess.com?
privateiptvaccess.com is placed in Toronto, Canada.
When does privateiptvaccess.com expire?
privateiptvaccess.com expires on 15 February 2028 according to https://rdap.verisign.com/com/v1/domain/privateiptvaccess.com.
Who owns privateiptvaccess.com?
The registry did not return a person or a company for privateiptvaccess.com. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/privateiptvaccess.com at 2026-10-30T14:10:27Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:10:27Z
- TLS source tls:443 at 2026-10-30T14:10:27Z
- HTTP source https://privateiptvaccess.com/ at 2026-10-30T14:10:27Z
- Tech source wappalyzergo at 2026-10-30T14:10:27Z
- Geo source db-ip at 2026-10-30T14:10:27Z
- Safety source family DNS and local lists at 2026-10-30T14:10:27Z
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.