twiigle.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 69 days left4 years oldTranco #839231
50
twiigle.com was registered on 20 Feb 2022 via Web Commerce Communications Limited dba WebNic.cc and the registry expiry is 20 Feb 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/twiigle.com.
twiigle.com publishes 2 nameservers. DNSSEC is not signed.
twiigle.com has 2 IPv4 addresses (104.21.89.83, 172.67.157.95) and 2 IPv6 addresses (2606:4700:3036::6815:5953, 2606:4700:3037::ac43:9d5f). The geolocation database places 104.21.89.83 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, Google Analytics, Google Hosted Libraries, HTTP/3, LiteSpeed, LiteSpeed Cache, Litespeed Cache, Unpkg and jQuery. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
twiigle.com was registered on 20 Feb 2022 via Web Commerce Communications Limited dba WebNic.cc. The registry returned 3 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/twiigle.com.
| Registered | since 20 Feb 2022 |
|---|---|
| Created | 20 February 2022 |
| Updated | 24 November 2024 |
| Expires | 20 February 2027 |
| Registrar | Web Commerce Communications Limited dba WebNic.cc |
| Status | client delete prohibited, client transfer prohibited, client update prohibited |
| Nameservers | lisa.ns.cloudflare.com, memphis.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/twiigle.com |
twiigle.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.
twiigle.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.
twiigle.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 lisa.ns.cloudflare.com is published for twiigle.com in the registration record from https://rdap.verisign.com/com/v1/domain/twiigle.com.
Nameserver memphis.ns.cloudflare.com is published for twiigle.com in the registration record from https://rdap.verisign.com/com/v1/domain/twiigle.com.
DNS
twiigle.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.89.83, 172.67.157.95 |
|---|---|
| AAAA | 2606:4700:3036::6815:5953, 2606:4700:3037::ac43:9d5f |
| NS | lisa.ns.cloudflare.com, memphis.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.89.83 answers for twiigle.com at resolver 1.1.1.1:53.
IPv4 address 172.67.157.95 answers for twiigle.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3036::6815:5953 answers for twiigle.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::ac43:9d5f answers for twiigle.com at resolver 1.1.1.1:53.
Hosting and geo
twiigle.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.89.83 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for twiigle.com is valid, with 69 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | twiigle.com |
| Valid from | 10 October 2026 |
| Valid until | 8 January 2027 |
| Days left | 69 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.twiigle.com, twiigle.com.
Tech stack
Tech detection checked the fetched homepage and named 10 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Cloudflare · CDN
- Google Analytics · Analytics
- Google Hosted Libraries · CDN
- HTTP/3 · Miscellaneous
- LiteSpeed · Web servers
- LiteSpeed Cache · Caching, WordPress plugins
- Litespeed Cache · Caching, WordPress plugins
- Unpkg · CDN
- jQuery · JavaScript libraries
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.
LiteSpeed is filed under Web servers.
LiteSpeed Cache is filed under Caching, WordPress plugins.
Litespeed Cache is filed under Caching, WordPress plugins.
Unpkg is filed under CDN.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 3244 ms. The target title is 31 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 3244 ms |
| Title length | 31 yes |
| Quoted title | "Twitter動画保存ランキング（24h） | Twiigle" |
| Meta description | "みんながダウンロード保存したTwitterエロ動画 | TwiigleはTwitterAPIでJapanでの動画ダウンロードランキングを自動表示するtwitter保存ランキングSearchEngine" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://twiigle.com/index.html |
| Language | ja |
| Links | 141 |
| Images | 60 |
| 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 twiigle.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 twiigle.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 0 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 twiigle.com safe?
Cloudflare family DNS returned a block for twiigle.com. That resolver covers adult and malware names.
Who hosts twiigle.com?
twiigle.com is placed in Toronto, Canada.
When does twiigle.com expire?
twiigle.com expires on 20 February 2027 according to https://rdap.verisign.com/com/v1/domain/twiigle.com.
Who owns twiigle.com?
The registry did not return a person or a company for twiigle.com. RDAP often redacts the registrant. The registrar on file is Web Commerce Communications Limited dba WebNic.cc.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/twiigle.com at 2026-10-30T14:18:13Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:18:13Z
- TLS source tls:443 at 2026-10-30T14:18:13Z
- HTTP source https://twiigle.com/ at 2026-10-30T14:18:13Z
- Tech source wappalyzergo at 2026-10-30T14:18:13Z
- Geo source db-ip at 2026-10-30T14:18:13Z
- Safety source family DNS and local lists at 2026-10-30T14:18:13Z
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.