sportsurge.cc
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe6 years old
30
sportsurge.cc was registered on 22 Sep 2020 via NameCheap, Inc. and the registry expiry is 22 Sep 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/sportsurge.cc.
sportsurge.cc publishes 2 nameservers. DNSSEC is not signed.
sportsurge.cc has 2 IPv4 addresses (104.219.250.37, 2.59.170.20). The geolocation database places 104.219.250.37 in Phoenix (Southbank), United States.
No safety warning was recorded for sportsurge.cc in the checks that ran.
Domain · RDAP/WHOIS
sportsurge.cc was registered on 22 Sep 2020 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/sportsurge.cc.
| Registered | since 22 Sep 2020 |
|---|---|
| Created | 22 September 2020 |
| Updated | 23 September 2026 |
| Expires | 22 September 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | dns101.registrar-servers.com, dns102.registrar-servers.com |
| DNSSEC | no |
| Source | https://tld-rdap.verisign.com/cc/v1/domain/sportsurge.cc |
sportsurge.cc 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 dns101.registrar-servers.com is published for sportsurge.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/sportsurge.cc.
Nameserver dns102.registrar-servers.com is published for sportsurge.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/sportsurge.cc.
DNS
sportsurge.cc has 2 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.219.250.37, 2.59.170.20 |
|---|---|
| AAAA | — |
| NS | ns1.lander.d.parity.domains, ns2.lander.d.parity.domains |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.219.250.37 answers for sportsurge.cc at resolver 1.1.1.1:53.
IPv4 address 2.59.170.20 answers for sportsurge.cc at resolver 1.1.1.1:53.
A random label under sportsurge.cc also resolved, which means wildcard DNS is on.
Hosting and geo
sportsurge.cc is placed in Phoenix (Southbank), United States by the local geolocation database (db-ip).
| Address | 104.219.250.37 |
|---|---|
| Country | United States |
| City | Phoenix (Southbank) |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for sportsurge.cc on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
EOF
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 |
|---|
context deadline exceeded
Security
Family DNS for sportsurge.cc 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 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: geo city changed from empty to Phoenix (Southbank).
- October 2026: geo country changed from empty to United States.
Questions
Is sportsurge.cc 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 sportsurge.cc?
sportsurge.cc is placed in Phoenix (Southbank), United States.
When does sportsurge.cc expire?
sportsurge.cc expires on 22 September 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/sportsurge.cc.
Who owns sportsurge.cc?
The registry did not return a person or a company for sportsurge.cc. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://tld-rdap.verisign.com/cc/v1/domain/sportsurge.cc at 2026-10-30T13:35:15Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:35:15Z
- TLS source tls:443 at 2026-10-30T13:35:15Z
- HTTP source https://sportsurge.cc/ at 2026-10-30T13:35:15Z
- Tech source not available at 2026-10-30T13:35:15Z
- Geo source db-ip at 2026-10-30T13:35:15Z
- Safety source family DNS and local lists at 2026-10-30T13:35:15Z
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.