animeindy.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 69 days left6 years old
70
animeindy.com was registered on 21 Oct 2020 via HOSTINGER operations, UAB and the registry expiry is 21 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/animeindy.com.
animeindy.com publishes 2 nameservers. DNSSEC is not signed.
animeindy.com has 2 IPv4 addresses (104.21.62.204, 172.67.139.61) and 2 IPv6 addresses (2606:4700:3030::6815:3ecc, 2606:4700:3034::ac43:8b3d). The geolocation database places 104.21.62.204 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 69 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, HTTP/3, MySQL, PHP, Perfmatters, Super Page Cache, WordPress, jQuery, jQuery Migrate and jsDelivr. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for animeindy.com in the checks that ran.
Domain · RDAP/WHOIS
animeindy.com was registered on 21 Oct 2020 via HOSTINGER operations, UAB. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/animeindy.com.
| Registered | since 21 Oct 2020 |
|---|---|
| Created | 21 October 2020 |
| Updated | 24 September 2026 |
| Expires | 21 October 2027 |
| Registrar | HOSTINGER operations, UAB |
| Status | client transfer prohibited |
| Nameservers | harvey.ns.cloudflare.com, liv.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/animeindy.com |
animeindy.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 harvey.ns.cloudflare.com is published for animeindy.com in the registration record from https://rdap.verisign.com/com/v1/domain/animeindy.com.
Nameserver liv.ns.cloudflare.com is published for animeindy.com in the registration record from https://rdap.verisign.com/com/v1/domain/animeindy.com.
DNS
animeindy.com has 4 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.62.204, 172.67.139.61 |
|---|---|
| AAAA | 2606:4700:3030::6815:3ecc, 2606:4700:3034::ac43:8b3d |
| NS | harvey.ns.cloudflare.com, liv.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 | absent |
| DMARC | absent |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.62.204 answers for animeindy.com at resolver 1.1.1.1:53.
IPv4 address 172.67.139.61 answers for animeindy.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3030::6815:3ecc answers for animeindy.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::ac43:8b3d answers for animeindy.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
animeindy.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.62.204 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for animeindy.com is valid, with 69 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | animeindy.com |
| Valid from | 11 October 2026 |
| Valid until | 9 January 2027 |
| Days left | 69 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.animeindy.com, animeindy.com.
Tech stack
Tech detection checked the fetched homepage and named 11 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
- MySQL · Databases
- PHP · Programming languages
- Perfmatters · WordPress plugins, Performance
- Super Page Cache · Caching, WordPress plugins
- WordPress · CMS, Blogs
- jQuery · JavaScript libraries
- jQuery Migrate · JavaScript libraries
- jsDelivr · CDN
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
MySQL is filed under Databases.
PHP is filed under Programming languages.
Perfmatters is filed under WordPress plugins, Performance.
Super Page Cache is filed under Caching, WordPress plugins.
WordPress is filed under CMS, Blogs.
jQuery is filed under JavaScript libraries.
jQuery Migrate is filed under JavaScript libraries.
jsDelivr is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 883 ms. The target title is 36 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 883 ms |
| Title length | 36 yes |
| Quoted title | "ANIMEiNDY - อนิเมะอินดี้ ดูอนิเมะฟรี" |
| Meta description | "ANIMEiNDY อนิเมะอินดี้ เว็บไซต์ดูอนิเมะ การ์ตูน อนิเมะจีน อนิเมะพากย์ไทย ซับไทย ติดตามอนิเมะโปรด อนิเมะใหม่ 2023 ติดตามข่าวสารอนิเมะ มากมาย" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | follow, index |
| Canonical | https://indy-anime.net/ |
| Language | th |
| Links | 273 |
| Images | 74 |
| 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 animeindy.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 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 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
First checked on 30 October 2026; changes will appear here.
Questions
Is animeindy.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 animeindy.com?
animeindy.com is placed in Toronto, Canada.
When does animeindy.com expire?
animeindy.com expires on 21 October 2027 according to https://rdap.verisign.com/com/v1/domain/animeindy.com.
Who owns animeindy.com?
The registry did not return a person or a company for animeindy.com. RDAP often redacts the registrant. The registrar on file is HOSTINGER operations, UAB.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/animeindy.com at 2026-10-30T13:44:31Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:44:31Z
- TLS source tls:443 at 2026-10-30T13:44:31Z
- HTTP source https://animeindy.com/ at 2026-10-30T13:44:31Z
- Tech source wappalyzergo at 2026-10-30T13:44:31Z
- Geo source db-ip at 2026-10-30T13:44:31Z
- Safety source family DNS and local lists at 2026-10-30T13:44:31Z
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.