callescort.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 75 days left11 years oldTranco #22028
75
callescort.org was registered on 28 Dec 2014 via Name.com, Inc. and the registry expiry is 28 Dec 2026. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/callescort.org.
callescort.org publishes 2 nameservers. DNSSEC is not signed.
callescort.org has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.4 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 75 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, FitVids.JS, Google Analytics, HTTP/3, PHP, jQuery, jQuery CDN and jQuery UI. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for callescort.org in the checks that ran.
Domain · RDAP/WHOIS
callescort.org was registered on 28 Dec 2014 via Name.com, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/callescort.org.
| Registered | since 28 Dec 2014 |
|---|---|
| Created | 28 December 2014 |
| Updated | 12 August 2026 |
| Expires | 28 December 2026 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited |
| Nameservers | armfazh.ns.cloudflare.com, perla.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/callescort.org |
callescort.org 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 armfazh.ns.cloudflare.com is published for callescort.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/callescort.org.
Nameserver perla.ns.cloudflare.com is published for callescort.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/callescort.org.
DNS
callescort.org has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.4, 188.114.97.4 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | armfazh.ns.cloudflare.com, perla.ns.cloudflare.com |
| MX | route3.mx.cloudflare.net (2), route1.mx.cloudflare.net (25), route2.mx.cloudflare.net (49) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at callescort.org is "v=spf1 ip4:194.107.126.0/24 ip4:45.63.54.0/24 include:_spf.mx.cloudflare.net ~all".
The DMARC text record at _dmarc.callescort.org is "v=DMARC1; p=reject; rua=mailto:[email protected]".
IPv4 address 188.114.96.4 answers for callescort.org at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for callescort.org at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for callescort.org at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for callescort.org at resolver 1.1.1.1:53.
Mail exchanger route3.mx.cloudflare.net has preference 2.
Mail exchanger route1.mx.cloudflare.net has preference 25.
Mail exchanger route2.mx.cloudflare.net has preference 49.
A random label under callescort.org also resolved, which means wildcard DNS is on.
Hosting and geo
callescort.org is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.4 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for callescort.org is valid, with 75 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | callescort.org |
| Valid from | 16 October 2026 |
| Valid until | 14 January 2027 |
| Days left | 75 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.callescort.org, callescort.org.
Tech stack
Tech detection checked the fetched homepage and named 8 products. Source: wappalyzergo.
- Cloudflare · CDN
- FitVids.JS · Widgets, Video players
- Google Analytics · Analytics
- HTTP/3 · Miscellaneous
- PHP · Programming languages
- jQuery · JavaScript libraries
- jQuery CDN · CDN
- jQuery UI · JavaScript libraries
Cloudflare is filed under CDN.
FitVids.JS is filed under Widgets, Video players.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
PHP is filed under Programming languages.
jQuery is filed under JavaScript libraries.
jQuery CDN is filed under CDN.
jQuery UI is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 42 ms. The target title is 59 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 42 ms |
| Title length | 59 yes |
| Quoted title | "Escorts in Las Vegas, escort phone numbers, photos, ratings" |
| Meta description | "Escorts in Las Vegas escorts, phone nubmers, reviews, pictures and videos" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 429 |
| Images | 17 |
| 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 callescort.org 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 10 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 callescort.org 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 callescort.org?
callescort.org is placed in Toronto, Canada.
When does callescort.org expire?
callescort.org expires on 28 December 2026 according to https://rdap.publicinterestregistry.org/rdap/domain/callescort.org.
Who owns callescort.org?
The registry did not return a person or a company for callescort.org. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/callescort.org at 2026-10-30T15:01:43Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:01:43Z
- TLS source tls:443 at 2026-10-30T15:01:43Z
- HTTP source https://callescort.org/ at 2026-10-30T15:01:43Z
- Tech source wappalyzergo at 2026-10-30T15:01:43Z
- Geo source db-ip at 2026-10-30T15:01:43Z
- Safety source family DNS and local lists at 2026-10-30T15:01:43Z
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.