clipf.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 62 days left14 years oldTranco #376671
50
clipf.com was registered on 29 Apr 2012 via PDR Ltd. d/b/a PublicDomainRegistry.com and the registry expiry is 29 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/clipf.com.
clipf.com publishes 2 nameservers. DNSSEC is not signed.
clipf.com has 1 IPv4 address (162.244.35.53). The geolocation database places 162.244.35.53 in Santa Clara, United States.
The TLS certificate from YE2 is valid and has 62 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Nginx. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
clipf.com was registered on 29 Apr 2012 via PDR Ltd. d/b/a PublicDomainRegistry.com. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/clipf.com.
| Registered | since 29 Apr 2012 |
|---|---|
| Created | 29 April 2012 |
| Updated | 20 April 2026 |
| Expires | 29 April 2027 |
| Registrar | PDR Ltd. d/b/a PublicDomainRegistry.com |
| Status | client transfer prohibited |
| Nameservers | ns1.xnlog.com, ns2.xnlog.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/clipf.com |
clipf.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.
Nameserver ns1.xnlog.com is published for clipf.com in the registration record from https://rdap.verisign.com/com/v1/domain/clipf.com.
Nameserver ns2.xnlog.com is published for clipf.com in the registration record from https://rdap.verisign.com/com/v1/domain/clipf.com.
DNS
clipf.com has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 162.244.35.53 |
|---|---|
| AAAA | — |
| NS | ns1.xnlog.com, ns2.xnlog.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 162.244.35.53 answers for clipf.com at resolver 1.1.1.1:53.
A random label under clipf.com also resolved, which means wildcard DNS is on.
Hosting and geo
clipf.com is placed in Santa Clara, United States by the local geolocation database (db-ip).
| Address | 162.244.35.53 |
|---|---|
| Country | United States |
| City | Santa Clara |
| Source | db-ip |
SSL/TLS
The certificate for clipf.com is valid, with 62 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | clipf.com |
| Valid from | 3 October 2026 |
| Valid until | 1 January 2027 |
| Days left | 62 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.clipf.com, clipf.com.
Tech stack
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
- Nginx · Web servers, Reverse proxies
Nginx is filed under Web servers, Reverse proxies.
On-page checks
The homepage returned HTTP 200 in 172 ms. The target title is 9 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 172 ms |
| Title length | 9 yes |
| Quoted title | "Clip Fuck" |
| Meta description | "Clips about the F... word. All clips are Free" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 122 |
| Images | 60 |
| 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 clipf.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 clipf.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 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 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: geo city changed from empty to Santa Clara.
- October 2026: geo country changed from empty to United States.
Questions
Is clipf.com safe?
Cloudflare family DNS returned a block for clipf.com. That resolver covers adult and malware names.
Who hosts clipf.com?
clipf.com is placed in Santa Clara, United States.
When does clipf.com expire?
clipf.com expires on 29 April 2027 according to https://rdap.verisign.com/com/v1/domain/clipf.com.
Who owns clipf.com?
The registry did not return a person or a company for clipf.com. RDAP often redacts the registrant. The registrar on file is PDR Ltd. d/b/a PublicDomainRegistry.com.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/clipf.com at 2026-10-30T13:49:57Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:49:57Z
- TLS source tls:443 at 2026-10-30T13:49:57Z
- HTTP source https://clipf.com/ at 2026-10-30T13:49:57Z
- Tech source wappalyzergo at 2026-10-30T13:49:57Z
- Geo source db-ip at 2026-10-30T13:49:57Z
- Safety source family DNS and local lists at 2026-10-30T13:49:57Z
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.