alpharatio.cc
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
80
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
80
alpharatio.cc was registered on 17 Aug 2013 via NameCheap, Inc. and the registry expiry is 17 Aug 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/alpharatio.cc.
alpharatio.cc publishes 2 nameservers. DNSSEC is not signed.
alpharatio.cc has 2 IPv4 addresses (104.21.31.58, 172.67.175.52). The geolocation database places 104.21.31.58 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 55 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for alpharatio.cc in the checks that ran.
alpharatio.cc was registered on 17 Aug 2013 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/alpharatio.cc.
| Registered | since 17 Aug 2013 |
|---|---|
| Created | 17 August 2013 |
| Updated | 18 July 2026 |
| Expires | 17 August 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | amit.ns.cloudflare.com, lucy.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://tld-rdap.verisign.com/cc/v1/domain/alpharatio.cc |
alpharatio.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 amit.ns.cloudflare.com is published for alpharatio.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/alpharatio.cc.
Nameserver lucy.ns.cloudflare.com is published for alpharatio.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/alpharatio.cc.
alpharatio.cc has 2 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.31.58, 172.67.175.52 |
|---|---|
| AAAA | — |
| NS | amit.ns.cloudflare.com, lucy.ns.cloudflare.com |
| MX | perseus.alpharatio.cc (10) |
| SPF | present |
| DMARC | present |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at alpharatio.cc is "v=spf1 mx a ip4:85.17.146.51/32 -all".
The DMARC text record at _dmarc.alpharatio.cc is "v=DMARC1; p=reject".
IPv4 address 104.21.31.58 answers for alpharatio.cc at resolver 1.1.1.1:53.
IPv4 address 172.67.175.52 answers for alpharatio.cc at resolver 1.1.1.1:53.
Mail exchanger perseus.alpharatio.cc has preference 10.
alpharatio.cc is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.31.58 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for alpharatio.cc is valid, with 55 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | alpharatio.cc |
| Valid from | 27 September 2026 |
| Valid until | 26 December 2026 |
| Days left | 55 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.alpharatio.cc, alpharatio.cc.
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
The homepage returned HTTP 200 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 0 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for alpharatio.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.
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 15 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.
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.
alpharatio.cc is placed in Toronto, Canada.
alpharatio.cc expires on 17 August 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/alpharatio.cc.
The registry did not return a person or a company for alpharatio.cc. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
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.