torontopassions.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
75
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
75
torontopassions.com was registered on 30 Nov 2004 via GoDaddy.com, LLC and the registry expiry is 21 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/torontopassions.com.
torontopassions.com publishes 2 nameservers. DNSSEC is not signed.
torontopassions.com has 3 IPv4 addresses (104.26.6.137, 104.26.7.137, 172.67.68.158) and 3 IPv6 addresses (2606:4700:20::681a:689, 2606:4700:20::681a:789, 2606:4700:20::ac43:449e). The geolocation database places 104.26.6.137 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 59 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Elementor, HTTP/3, MySQL, PHP, Perfmatters, Site Kit, WP Rocket and WordPress. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for torontopassions.com in the checks that ran.
torontopassions.com was registered on 30 Nov 2004 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/torontopassions.com.
| Registered | since 30 Nov 2004 |
|---|---|
| Created | 30 November 2004 |
| Updated | 1 July 2024 |
| Expires | 21 May 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | logan.ns.cloudflare.com, nia.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/torontopassions.com |
torontopassions.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.
torontopassions.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
torontopassions.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.
torontopassions.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 logan.ns.cloudflare.com is published for torontopassions.com in the registration record from https://rdap.verisign.com/com/v1/domain/torontopassions.com.
Nameserver nia.ns.cloudflare.com is published for torontopassions.com in the registration record from https://rdap.verisign.com/com/v1/domain/torontopassions.com.
torontopassions.com has 6 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.6.137, 104.26.7.137, 172.67.68.158 |
|---|---|
| AAAA | 2606:4700:20::681a:689, 2606:4700:20::681a:789, 2606:4700:20::ac43:449e |
| NS | logan.ns.cloudflare.com, nia.ns.cloudflare.com |
| MX | mx1-usg2.ppe-hosted.com (0), mx2-usg2.ppe-hosted.com (0), mx3-usg2.ppe-hosted.com (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at torontopassions.com is "v=spf1 include:secureserver.net -all".
IPv4 address 104.26.6.137 answers for torontopassions.com at resolver 1.1.1.1:53.
IPv4 address 104.26.7.137 answers for torontopassions.com at resolver 1.1.1.1:53.
IPv4 address 172.67.68.158 answers for torontopassions.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:689 answers for torontopassions.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:789 answers for torontopassions.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:449e answers for torontopassions.com at resolver 1.1.1.1:53.
Mail exchanger mx1-usg2.ppe-hosted.com has preference 0.
Mail exchanger mx2-usg2.ppe-hosted.com has preference 0.
Mail exchanger mx3-usg2.ppe-hosted.com has preference 0.
torontopassions.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.6.137 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for torontopassions.com is valid, with 59 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | torontopassions.com |
| Valid from | 1 October 2026 |
| Valid until | 30 December 2026 |
| Days left | 59 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.torontopassions.com, torontopassions.com.
Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
Elementor is filed under Page builders, WordPress plugins.
HTTP/3 is filed under Miscellaneous.
MySQL is filed under Databases.
PHP is filed under Programming languages.
Perfmatters is filed under WordPress plugins, Performance.
Site Kit is filed under Analytics, WordPress plugins.
WP Rocket is filed under Caching, WordPress plugins.
WordPress is filed under CMS, Blogs.
The homepage returned HTTP 200 in 466 ms. The target title is 57 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 466 ms |
| Title length | 57 yes |
| Quoted title | "Toronto Escorts Escort Agency by Toronto Passions Escorts" |
| Meta description | "Toronto Escorts Agency by Toronto Passions Escorts Providing Elite Escorts ❤️ Recognized as #1 from all Toronto Escort Agencies - 416-599-9669" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large |
| Canonical | https://www.torontopassions.com |
| Language | en-US |
| Links | 110 |
| Images | 42 |
| 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 torontopassions.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.
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 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.
torontopassions.com is placed in Toronto, Canada.
torontopassions.com expires on 21 May 2027 according to https://rdap.verisign.com/com/v1/domain/torontopassions.com.
The registry did not return a person or a company for torontopassions.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
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.