redgif.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 29 days left7 years old
55
redgif.com was registered on 22 Feb 2019 via GoDaddy.com, LLC and the registry expiry is 22 Feb 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/redgif.com.
redgif.com publishes 2 nameservers. DNSSEC is not signed.
redgif.com has 2 IPv4 addresses (104.21.65.135, 172.67.163.162) and 2 IPv6 addresses (2606:4700:3033::6815:4187, 2606:4700:3037::ac43:a3a2). The geolocation database places 104.21.65.135 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 29 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apple Sign-in, Cloudflare, Envoy, Google Analytics, Node.js, Nuxt.js and Vue.js. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
redgif.com was registered on 22 Feb 2019 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/redgif.com.
| Registered | since 22 Feb 2019 |
|---|---|
| Created | 22 February 2019 |
| Updated | 23 February 2026 |
| Expires | 22 February 2028 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | beth.ns.cloudflare.com, lars.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/redgif.com |
redgif.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.
redgif.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
redgif.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.
redgif.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 beth.ns.cloudflare.com is published for redgif.com in the registration record from https://rdap.verisign.com/com/v1/domain/redgif.com.
Nameserver lars.ns.cloudflare.com is published for redgif.com in the registration record from https://rdap.verisign.com/com/v1/domain/redgif.com.
DNS
redgif.com has 4 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.65.135, 172.67.163.162 |
|---|---|
| AAAA | 2606:4700:3033::6815:4187, 2606:4700:3037::ac43:a3a2 |
| NS | beth.ns.cloudflare.com, lars.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at redgif.com is "v=spf1 include:_spf.google.com -all".
IPv4 address 104.21.65.135 answers for redgif.com at resolver 1.1.1.1:53.
IPv4 address 172.67.163.162 answers for redgif.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3033::6815:4187 answers for redgif.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::ac43:a3a2 answers for redgif.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
redgif.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.65.135 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for redgif.com is valid, with 29 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | redgif.com |
| Valid from | 1 September 2026 |
| Valid until | 30 November 2026 |
| Days left | 29 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.redgif.com, redgif.com.
Tech stack
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
- Apple Sign-in · Authentication
- Cloudflare · CDN
- Envoy · Reverse proxies
- Google Analytics · Analytics
- Node.js · Programming languages
- Nuxt.js · JavaScript frameworks, Web frameworks, Web servers, Static site generator
- Vue.js · JavaScript frameworks
Apple Sign-in is filed under Authentication.
Cloudflare is filed under CDN.
Envoy is filed under Reverse proxies.
Google Analytics is filed under Analytics.
Node.js is filed under Programming languages.
Nuxt.js is filed under JavaScript frameworks, Web frameworks, Web servers, Static site generator.
Vue.js is filed under JavaScript frameworks.
On-page checks
The homepage returned HTTP 200 in 28 ms. The target title is 40 characters and the page has 2 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 28 ms |
| Title length | 40 yes |
| Quoted title | "xfree.com | Free Porn Reels & NSFW Nudes" |
| Meta description | "Watch trendy TikTok shorts & reels porn for free! Discover new trending xxx porn reels, follow NSFW influencers, or upload your own sex leaks!" yes |
| H1 count | 2 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://www.xfree.com?country=DE |
| Language | en |
| Links | 78 |
| Images | 131 |
| 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 redgif.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 redgif.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 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
First checked on 30 October 2026; changes will appear here.
Questions
Is redgif.com safe?
Cloudflare family DNS returned a block for redgif.com. That resolver covers adult and malware names.
Who hosts redgif.com?
redgif.com is placed in Toronto, Canada.
When does redgif.com expire?
redgif.com expires on 22 February 2028 according to https://rdap.verisign.com/com/v1/domain/redgif.com.
Who owns redgif.com?
The registry did not return a person or a company for redgif.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/redgif.com at 2026-10-30T14:11:35Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:11:35Z
- TLS source tls:443 at 2026-10-30T14:11:35Z
- HTTP source https://redgif.com/ at 2026-10-30T14:11:35Z
- Tech source wappalyzergo at 2026-10-30T14:11:35Z
- Geo source db-ip at 2026-10-30T14:11:35Z
- Safety source family DNS and local lists at 2026-10-30T14:11:35Z
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.