aiosearch.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 70 days left19 years old
55
aiosearch.com was registered on 27 Feb 2007 via easyDNS Technologies Inc. and the registry expiry is 27 Feb 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/aiosearch.com.
aiosearch.com publishes 2 nameservers. DNSSEC is not signed.
aiosearch.com has 2 IPv4 addresses (104.21.54.118, 172.67.138.122) and 2 IPv6 addresses (2606:4700:3031::6815:3676, 2606:4700:3037::ac43:8a7a). The geolocation database places 104.21.54.118 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 70 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Browser Insights and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
aiosearch.com was registered on 27 Feb 2007 via easyDNS Technologies Inc.. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/aiosearch.com.
| Registered | since 27 Feb 2007 |
|---|---|
| Created | 27 February 2007 |
| Updated | 13 October 2025 |
| Expires | 27 February 2027 |
| Registrar | easyDNS Technologies Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | rosemary.ns.cloudflare.com, zod.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/aiosearch.com |
aiosearch.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.
aiosearch.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 rosemary.ns.cloudflare.com is published for aiosearch.com in the registration record from https://rdap.verisign.com/com/v1/domain/aiosearch.com.
Nameserver zod.ns.cloudflare.com is published for aiosearch.com in the registration record from https://rdap.verisign.com/com/v1/domain/aiosearch.com.
DNS
aiosearch.com has 4 address records, 7 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.54.118, 172.67.138.122 |
|---|---|
| AAAA | 2606:4700:3031::6815:3676, 2606:4700:3037::ac43:8a7a |
| NS | rosemary.ns.cloudflare.com, zod.ns.cloudflare.com |
| MX | aspmx.l.google.com (10) Google, alt1.aspmx.l.google.com (20) Google, alt2.aspmx.l.google.com (20) Google, aspmx2.googlemail.com (30) Google, aspmx3.googlemail.com (30) Google, aspmx4.googlemail.com (30) Google, aspmx5.googlemail.com (30) Google |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at aiosearch.com is "v=spf1 include:mailgun.org include:spf.improvmx.com ~all".
IPv4 address 104.21.54.118 answers for aiosearch.com at resolver 1.1.1.1:53.
IPv4 address 172.67.138.122 answers for aiosearch.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::6815:3676 answers for aiosearch.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::ac43:8a7a answers for aiosearch.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 20. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 20. The host is recognised as Google.
Mail exchanger aspmx2.googlemail.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx3.googlemail.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx4.googlemail.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx5.googlemail.com has preference 30. The host is recognised as Google.
A random label under aiosearch.com also resolved, which means wildcard DNS is on.
Hosting and geo
aiosearch.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.54.118 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for aiosearch.com is valid, with 70 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | aiosearch.com |
| Valid from | 12 October 2026 |
| Valid until | 10 January 2027 |
| Days left | 70 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.aiosearch.com, aiosearch.com.
Tech stack
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 63 ms. The target title is 34 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 63 ms |
| Title length | 34 yes |
| Quoted title | "AIO Search - Search Torrents Sites" |
| Meta description | "Torrents Category, Torrent finder is a bit torrent multi search engine 🚀 which searches 129 torrent sites and trackers from one page, write your torrent keywords then check on your favorite torrent sites and trackers to start your search." yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index,follow |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| 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 aiosearch.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 aiosearch.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 aiosearch.com safe?
Cloudflare family DNS returned a block for aiosearch.com. That resolver covers adult and malware names.
Who hosts aiosearch.com?
aiosearch.com is placed in Toronto, Canada.
When does aiosearch.com expire?
aiosearch.com expires on 27 February 2027 according to https://rdap.verisign.com/com/v1/domain/aiosearch.com.
Who owns aiosearch.com?
The registry did not return a person or a company for aiosearch.com. RDAP often redacts the registrant. The registrar on file is easyDNS Technologies Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/aiosearch.com at 2026-10-30T13:43:36Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:43:36Z
- TLS source tls:443 at 2026-10-30T13:43:36Z
- HTTP source https://aiosearch.com/ at 2026-10-30T13:43:36Z
- Tech source wappalyzergo at 2026-10-30T13:43:36Z
- Geo source db-ip at 2026-10-30T13:43:36Z
- Safety source family DNS and local lists at 2026-10-30T13:43:36Z
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.