scorexer.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 2 days left6 years old
35
scorexer.com was registered on 3 Jan 2020 via Squarespace Domains II LLC and the registry expiry is 3 Jan 2032. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/scorexer.com.
scorexer.com publishes 4 nameservers. DNSSEC is signed.
scorexer.com has 1 IPv4 address (52.23.76.128). The geolocation database places 52.23.76.128 in Ashburn, United States.
The TLS certificate from YE2 is not valid (TLS 1.3).
No safety warning was recorded for scorexer.com in the checks that ran.
Domain · RDAP/WHOIS
scorexer.com was registered on 3 Jan 2020 via Squarespace Domains II LLC. The registry returned 2 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/scorexer.com.
| Registered | since 3 Jan 2020 |
|---|---|
| Created | 3 January 2020 |
| Updated | 4 June 2024 |
| Expires | 3 January 2032 |
| Registrar | Squarespace Domains II LLC |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/scorexer.com |
scorexer.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.
scorexer.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-cloud-a1.googledomains.com is published for scorexer.com in the registration record from https://rdap.verisign.com/com/v1/domain/scorexer.com.
Nameserver ns-cloud-a2.googledomains.com is published for scorexer.com in the registration record from https://rdap.verisign.com/com/v1/domain/scorexer.com.
Nameserver ns-cloud-a3.googledomains.com is published for scorexer.com in the registration record from https://rdap.verisign.com/com/v1/domain/scorexer.com.
Nameserver ns-cloud-a4.googledomains.com is published for scorexer.com in the registration record from https://rdap.verisign.com/com/v1/domain/scorexer.com.
DNS
scorexer.com has 1 address record, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 52.23.76.128 |
|---|---|
| AAAA | — |
| NS | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 52.23.76.128 answers for scorexer.com at resolver 1.1.1.1:53.
A random label under scorexer.com also resolved, which means wildcard DNS is on.
Hosting and geo
scorexer.com is placed in Ashburn, United States by the local geolocation database (db-ip).
| Address | 52.23.76.128 |
|---|---|
| Country | United States |
| City | Ashburn |
| Source | db-ip |
SSL/TLS
The certificate for scorexer.com is not valid, with 2 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | *.disputeprocess.com |
| Valid from | 4 August 2026 |
| Valid until | 2 November 2026 |
| Days left | 2 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.disputeprocess.com, disputeprocess.com.
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://scorexer.com/": tls: failed to verify certificate: x509: certificate is valid for *.disputeprocess.com, disputeprocess.com, not scorexer.com
Security
Family DNS for scorexer.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 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 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 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: geo city changed from empty to Ashburn.
- October 2026: geo country changed from empty to United States.
Questions
Is scorexer.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 scorexer.com?
scorexer.com is placed in Ashburn, United States.
When does scorexer.com expire?
scorexer.com expires on 3 January 2032 according to https://rdap.verisign.com/com/v1/domain/scorexer.com.
Who owns scorexer.com?
The registry did not return a person or a company for scorexer.com. RDAP often redacts the registrant. The registrar on file is Squarespace Domains II LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/scorexer.com at 2026-10-30T14:12:59Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:12:59Z
- TLS source tls:443 at 2026-10-30T14:12:59Z
- HTTP source https://scorexer.com/ at 2026-10-30T14:12:59Z
- Tech source not available at 2026-10-30T14:12:59Z
- Geo source db-ip at 2026-10-30T14:12:59Z
- Safety source family DNS and local lists at 2026-10-30T14:12:59Z
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.