csrscape.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 159 days left5 years old
65
csrscape.com was registered on 6 Mar 2021 via Amazon Registrar, Inc. and the registry expiry is 6 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/csrscape.com.
csrscape.com publishes 4 nameservers. DNSSEC is not signed.
csrscape.com has 4 IPv4 addresses (143.204.55.36, 143.204.55.44, 143.204.55.52, 143.204.55.56). The geolocation database places 143.204.55.36 in Zurich, Switzerland.
The TLS certificate from Amazon RSA 2048 S22 is valid and has 159 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Amazon CloudFront, Amazon Web Services, HTTP/3, Node.js, Nuxt.js and Vue.js. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for csrscape.com in the checks that ran.
Domain · RDAP/WHOIS
csrscape.com was registered on 6 Mar 2021 via Amazon Registrar, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/csrscape.com.
| Registered | since 6 Mar 2021 |
|---|---|
| Created | 6 March 2021 |
| Updated | 27 June 2026 |
| Expires | 6 March 2027 |
| Registrar | Amazon Registrar, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns-1321.awsdns-37.org, ns-1929.awsdns-49.co.uk, ns-352.awsdns-44.com, ns-809.awsdns-37.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/csrscape.com |
csrscape.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.
Nameserver ns-1321.awsdns-37.org is published for csrscape.com in the registration record from https://rdap.verisign.com/com/v1/domain/csrscape.com.
Nameserver ns-1929.awsdns-49.co.uk is published for csrscape.com in the registration record from https://rdap.verisign.com/com/v1/domain/csrscape.com.
Nameserver ns-352.awsdns-44.com is published for csrscape.com in the registration record from https://rdap.verisign.com/com/v1/domain/csrscape.com.
Nameserver ns-809.awsdns-37.net is published for csrscape.com in the registration record from https://rdap.verisign.com/com/v1/domain/csrscape.com.
DNS
csrscape.com has 4 address records, 5 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 143.204.55.36, 143.204.55.44, 143.204.55.52, 143.204.55.56 |
|---|---|
| AAAA | — |
| NS | ns-1321.awsdns-37.org, ns-1929.awsdns-49.co.uk, ns-352.awsdns-44.com, ns-809.awsdns-37.net |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 143.204.55.36 answers for csrscape.com at resolver 1.1.1.1:53.
IPv4 address 143.204.55.44 answers for csrscape.com at resolver 1.1.1.1:53.
IPv4 address 143.204.55.52 answers for csrscape.com at resolver 1.1.1.1:53.
IPv4 address 143.204.55.56 answers for csrscape.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
csrscape.com is placed in Zurich, Switzerland by the local geolocation database (db-ip).
| Address | 143.204.55.36 |
|---|---|
| Country | Switzerland |
| City | Zurich |
| Source | db-ip |
SSL/TLS
The certificate for csrscape.com is valid, with 159 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 S22 |
|---|---|
| Subject | *.csrscape.com |
| Valid from | 22 September 2026 |
| Valid until | 8 April 2027 |
| Days left | 159 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.csrscape.com, csrscape.com.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- Amazon CloudFront · CDN
- Amazon Web Services · PaaS
- HTTP/3 · Miscellaneous
- Node.js · Programming languages
- Nuxt.js · JavaScript frameworks, Web frameworks, Web servers, Static site generator
- Vue.js · JavaScript frameworks
Amazon CloudFront is filed under CDN.
Amazon Web Services is filed under PaaS.
HTTP/3 is filed under Miscellaneous.
Node.js is filed under Programming languages.
Nuxt.js is filed under JavaScript frameworks, Web frameworks, Web servers, Static site generator.
Vue.js is filed under JavaScript frameworks.
On-page checks
The homepage returned HTTP 200 in 2893 ms. The target title is 51 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 2893 ms |
| Title length | 51 yes |
| Quoted title | "CSRScape | Complete Contact Center Platform with AI" |
| Meta description | "CSRScape combines voice, email, SMS, live chat, customer management, AI agents, quality assurance, coaching, and performance analytics in one connected contact center platform." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 28 |
| Images | 15 |
| 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 csrscape.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.
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 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
- October 2026: dns a changed from 108.138.26.119,108.138.26.125,108.138.26.16,108.138.26.8 to 143.204.55.36,143.204.55.44,143.204.55.52,143.204.55.56.
Questions
Is csrscape.com 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 csrscape.com?
csrscape.com is placed in Zurich, Switzerland.
When does csrscape.com expire?
csrscape.com expires on 6 March 2027 according to https://rdap.verisign.com/com/v1/domain/csrscape.com.
Who owns csrscape.com?
The registry did not return a person or a company for csrscape.com. RDAP often redacts the registrant. The registrar on file is Amazon Registrar, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/csrscape.com at 2026-10-30T13:50:45Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:50:45Z
- TLS source tls:443 at 2026-10-30T13:50:45Z
- HTTP source https://csrscape.com/ at 2026-10-30T13:50:45Z
- Tech source wappalyzergo at 2026-10-30T13:50:45Z
- Geo source db-ip at 2026-10-30T13:50:45Z
- Safety source family DNS and local lists at 2026-10-30T13:50:45Z
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.