asianpinay.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 53 days left1 year oldTranco #109634
75
asianpinay.to was registered on 5 Jan 2025 via Spaceship, Inc. and the registry expiry is 6 Jan 2027. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/asianpinay.to.
asianpinay.to publishes 2 nameservers. DNSSEC is not signed.
asianpinay.to has 2 IPv4 addresses (104.21.19.89, 172.67.185.179) and 2 IPv6 addresses (2606:4700:3031::ac43:b9b3, 2606:4700:3035::6815:1359). The geolocation database places 104.21.19.89 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 53 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named AddToAny, AddToAny Share Buttons, Cloudflare, Cloudflare Browser Insights, HTTP/3, LiteSpeed, LiteSpeed Cache, Litespeed Cache, MySQL, PHP, WordPress, jQuery and jQuery Migrate. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
asianpinay.to was registered on 5 Jan 2025 via Spaceship, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/asianpinay.to.
| Registered | since 5 Jan 2025 |
|---|---|
| Created | 5 January 2025 |
| Updated | 3 January 2026 |
| Expires | 6 January 2027 |
| Registrar | Spaceship, Inc. |
| Status | active |
| Nameservers | anirban.ns.cloudflare.com, nucum.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/asianpinay.to |
Nameserver anirban.ns.cloudflare.com is published for asianpinay.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/asianpinay.to.
Nameserver nucum.ns.cloudflare.com is published for asianpinay.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/asianpinay.to.
DNS
asianpinay.to has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.19.89, 172.67.185.179 |
|---|---|
| AAAA | 2606:4700:3031::ac43:b9b3, 2606:4700:3035::6815:1359 |
| NS | anirban.ns.cloudflare.com, nucum.ns.cloudflare.com |
| MX | route1.mx.cloudflare.net (4), route3.mx.cloudflare.net (57), route2.mx.cloudflare.net (60) |
| SPF | present |
| DMARC | present |
| 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 |
The SPF text record at asianpinay.to is "v=spf1 include:_spf.mx.cloudflare.net ip4:198.186.130.214 ~all".
The DMARC text record at _dmarc.asianpinay.to is "v=DMARC1; p=none".
IPv4 address 104.21.19.89 answers for asianpinay.to at resolver 1.1.1.1:53.
IPv4 address 172.67.185.179 answers for asianpinay.to at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::ac43:b9b3 answers for asianpinay.to at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::6815:1359 answers for asianpinay.to at resolver 1.1.1.1:53.
Mail exchanger route1.mx.cloudflare.net has preference 4.
Mail exchanger route3.mx.cloudflare.net has preference 57.
Mail exchanger route2.mx.cloudflare.net has preference 60.
Hosting and geo
asianpinay.to is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.19.89 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for asianpinay.to is valid, with 53 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | asianpinay.to |
| Valid from | 24 September 2026 |
| Valid until | 24 December 2026 |
| Days left | 53 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.asianpinay.to, asianpinay.to.
Tech stack
Tech detection checked the fetched homepage and named 13 products. Source: wappalyzergo.
- AddToAny · Widgets
- AddToAny Share Buttons · WordPress plugins
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- HTTP/3 · Miscellaneous
- LiteSpeed · Web servers
- LiteSpeed Cache · Caching, WordPress plugins
- Litespeed Cache · Caching, WordPress plugins
- MySQL · Databases
- PHP · Programming languages
- WordPress · CMS, Blogs
- jQuery · JavaScript libraries
- jQuery Migrate · JavaScript libraries
AddToAny is filed under Widgets.
AddToAny Share Buttons is filed under WordPress plugins.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
HTTP/3 is filed under Miscellaneous.
LiteSpeed is filed under Web servers.
LiteSpeed Cache is filed under Caching, WordPress plugins.
Litespeed Cache is filed under Caching, WordPress plugins.
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.
On-page checks
The homepage returned HTTP 200 in 63 ms. The target title is 58 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 63 ms |
| Title length | 58 yes |
| Quoted title | "AsianPinay - Watch Asian, Pinay, Viral, Porn, & Sex Videos" |
| Meta description | "Find the latest Asian Pinay Viral Porn and Sex Scandals. The best Video Collection of Philippine Amateur Porn Videos featuring hot Asians and Filipina sex video scandals from different amateur porn sites are here for you to watch instantly." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | follow, index |
| Canonical | — |
| Language | en-US |
| Links | 364 |
| Images | 157 |
| 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 asianpinay.to 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 | yes |
Cloudflare family DNS returned a block for asianpinay.to. 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 15 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 10 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 asianpinay.to safe?
Cloudflare family DNS returned a block for asianpinay.to. That resolver covers adult and malware names.
Who hosts asianpinay.to?
asianpinay.to is placed in Toronto, Canada.
When does asianpinay.to expire?
asianpinay.to expires on 6 January 2027 according to https://rdap.tonicregistry.to/rdap/domain/asianpinay.to.
Who owns asianpinay.to?
The registry did not return a person or a company for asianpinay.to. RDAP often redacts the registrant. The registrar on file is Spaceship, Inc..
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/asianpinay.to at 2026-10-30T15:15:22Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:15:22Z
- TLS source tls:443 at 2026-10-30T15:15:22Z
- HTTP source https://asianpinay.to/ at 2026-10-30T15:15:22Z
- Tech source wappalyzergo at 2026-10-30T15:15:22Z
- Geo source db-ip at 2026-10-30T15:15:22Z
- Safety source family DNS and local lists at 2026-10-30T15:15:22Z
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.