blazecc.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 84 days left19 years oldTranco #622193
90
blazecc.com was registered on 3 Apr 2007 via GoDaddy.com, LLC and the registry expiry is 3 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/blazecc.com.
blazecc.com publishes 2 nameservers. DNSSEC is not signed.
blazecc.com has 2 IPv4 addresses (104.18.0.57, 104.18.1.57) and 2 IPv6 addresses (2606:4700::6812:139, 2606:4700::6812:39). The geolocation database places 104.18.0.57 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 84 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Azure Edge Network, Bootstrap, Cloudflare, Cloudflare Bot Management, Google Analytics, Google Tag Manager, HSTS, Microsoft ASP.NET and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for blazecc.com in the checks that ran.
Domain · RDAP/WHOIS
blazecc.com was registered on 3 Apr 2007 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/blazecc.com.
| Registered | since 3 Apr 2007 |
|---|---|
| Created | 3 April 2007 |
| Updated | 20 March 2025 |
| Expires | 3 April 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | dayana.ns.cloudflare.com, george.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/blazecc.com |
blazecc.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.
blazecc.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
blazecc.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.
blazecc.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver dayana.ns.cloudflare.com is published for blazecc.com in the registration record from https://rdap.verisign.com/com/v1/domain/blazecc.com.
Nameserver george.ns.cloudflare.com is published for blazecc.com in the registration record from https://rdap.verisign.com/com/v1/domain/blazecc.com.
DNS
blazecc.com has 4 address records, 4 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.18.0.57, 104.18.1.57 |
|---|---|
| AAAA | 2606:4700::6812:139, 2606:4700::6812:39 |
| NS | dayana.ns.cloudflare.com, george.ns.cloudflare.com |
| MX | mxa.blazecc.com (0), mxb.blazecc.com (0), cm1.blazecc.com (1), cm2.blazecc.com (2) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at blazecc.com is "v=spf1 mx include:spf-002e9f01.pphosted.com a:mail.capitalcardservices.com ip4:66.128.181.52 ip4:96.2.254.69 ip4:159.183.16.147 ip4:134.128.105.241 ~all".
The DMARC text record at _dmarc.blazecc.com is "v=DMARC1; p=reject; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected]".
IPv4 address 104.18.0.57 answers for blazecc.com at resolver 1.1.1.1:53.
IPv4 address 104.18.1.57 answers for blazecc.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700::6812:139 answers for blazecc.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700::6812:39 answers for blazecc.com at resolver 1.1.1.1:53.
Mail exchanger mxa.blazecc.com has preference 0.
Mail exchanger mxb.blazecc.com has preference 0.
Mail exchanger cm1.blazecc.com has preference 1.
Mail exchanger cm2.blazecc.com has preference 2.
Hosting and geo
blazecc.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.18.0.57 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for blazecc.com is valid, with 84 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | blazecc.com |
| Valid from | 26 October 2026 |
| Valid until | 24 January 2027 |
| Days left | 84 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.blazecc.com, blazecc.com.
Tech stack
Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.
- Azure Edge Network · Miscellaneous
- Bootstrap · UI frameworks
- Cloudflare · CDN
- Cloudflare Bot Management · Security
- Google Analytics · Analytics
- Google Tag Manager · Tag managers
- HSTS · Security
- Microsoft ASP.NET · Web frameworks
- jQuery · JavaScript libraries
Azure Edge Network is filed under Miscellaneous.
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
Cloudflare Bot Management is filed under Security.
Google Analytics is filed under Analytics.
Google Tag Manager is filed under Tag managers.
HSTS is filed under Security.
Microsoft ASP.NET is filed under Web frameworks.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 908 ms. The target title is 45 characters and the page has 13 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 908 ms |
| Title length | 45 yes |
| Quoted title | "Blaze Mastercard® - We Believe in Your Future" |
| Meta description | "Welcome to Blaze Mastercard Credit Card - where you can start achieving your credit goals and work towards financial freedom." yes |
| H1 count | 13 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | https://blazecc.com |
| Language | en |
| Links | 15 |
| Images | 14 |
| 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 blazecc.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 | yes |
| CSP | yes |
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 15 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 blazecc.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 blazecc.com?
blazecc.com is placed in Toronto, Canada.
When does blazecc.com expire?
blazecc.com expires on 3 April 2027 according to https://rdap.verisign.com/com/v1/domain/blazecc.com.
Who owns blazecc.com?
The registry did not return a person or a company for blazecc.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/blazecc.com at 2026-10-30T13:47:24Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:47:24Z
- TLS source tls:443 at 2026-10-30T13:47:24Z
- HTTP source https://blazecc.com/ at 2026-10-30T13:47:24Z
- Tech source wappalyzergo at 2026-10-30T13:47:24Z
- Geo source db-ip at 2026-10-30T13:47:24Z
- Safety source family DNS and local lists at 2026-10-30T13:47:24Z
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.