pelis24.blog
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
pelis24.blog was registered on 8 Jan 2020 via Namecheap and the registry expiry is 8 Jan 2027. WHOIS data came from RDAP at https://rdap.blog.fury.ca/rdap/domain/pelis24.blog.
pelis24.blog publishes 2 nameservers. DNSSEC is not signed.
pelis24.blog has 2 IPv4 addresses (104.21.52.198, 172.67.203.93) and 2 IPv6 addresses (2606:4700:3036::6815:34c6, 2606:4700:3037::ac43:cb5d). The geolocation database places 104.21.52.198 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 41 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, Google Analytics, Google Hosted Libraries, HTTP/3, MySQL, PHP, WordPress, jQuery and jQuery Migrate. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for pelis24.blog in the checks that ran.
pelis24.blog was registered on 8 Jan 2020 via Namecheap. The registry returned 1 status value and 2 nameservers from https://rdap.blog.fury.ca/rdap/domain/pelis24.blog.
| Registered | since 8 Jan 2020 |
|---|---|
| Created | 8 January 2020 |
| Updated | 12 January 2026 |
| Expires | 8 January 2027 |
| Registrar | Namecheap |
| Status | active |
| Nameservers | beau.ns.cloudflare.com, nola.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.blog.fury.ca/rdap/domain/pelis24.blog |
Nameserver beau.ns.cloudflare.com is published for pelis24.blog in the registration record from https://rdap.blog.fury.ca/rdap/domain/pelis24.blog.
Nameserver nola.ns.cloudflare.com is published for pelis24.blog in the registration record from https://rdap.blog.fury.ca/rdap/domain/pelis24.blog.
pelis24.blog has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.52.198, 172.67.203.93 |
|---|---|
| AAAA | 2606:4700:3036::6815:34c6, 2606:4700:3037::ac43:cb5d |
| NS | beau.ns.cloudflare.com, nola.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.52.198 answers for pelis24.blog at resolver 1.1.1.1:53.
IPv4 address 172.67.203.93 answers for pelis24.blog at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3036::6815:34c6 answers for pelis24.blog at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::ac43:cb5d answers for pelis24.blog at resolver 1.1.1.1:53.
A random label under pelis24.blog also resolved, which means wildcard DNS is on.
pelis24.blog is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.52.198 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for pelis24.blog is valid, with 41 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | pelis24.blog |
| Valid from | 13 September 2026 |
| Valid until | 12 December 2026 |
| Days left | 41 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.pelis24.blog, pelis24.blog.
Tech detection checked the fetched homepage and named 10 products. Source: wappalyzergo.
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
Google Analytics is filed under Analytics.
Google Hosted Libraries is filed under CDN.
HTTP/3 is filed under Miscellaneous.
MySQL is filed under Databases.
PHP is filed under Programming languages.
WordPress is filed under CMS, Blogs.
jQuery is filed under JavaScript libraries.
jQuery Migrate is filed under JavaScript libraries.
The homepage returned HTTP 200 in 121 ms. The target title is 53 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 121 ms |
| Title length | 53 yes |
| Quoted title | "▷ Pelis24 - Ver Películas Online Gratis HD en Español" |
| Meta description | "En Pelis24 ❤️ puedes ver películas online en HD. Aquí puedes descargar peliculas gratis, ver películas completas y en español." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | index,follow |
| Canonical | https://pelis24.blog/ |
| Language | es |
| Links | 1341 |
| Images | 129 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for pelis24.blog 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.
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 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.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
pelis24.blog is placed in Toronto, Canada.
pelis24.blog expires on 8 January 2027 according to https://rdap.blog.fury.ca/rdap/domain/pelis24.blog.
The registry did not return a person or a company for pelis24.blog. RDAP often redacts the registrant. The registrar on file is Namecheap.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.