blitzjs.com
Its Domain Power Rank is moderate.
- Global Rank
- #119,198
▲ 23,799
- Rank in TLD
- #51,736
▲ 8,882
- Referring Domains
- 167
▼ 1
- Avg. Referrer Power Rank
- 35.1
- Subdomains
- 3
- Domain age
- 6 yr 8 mo
Link Overview
- Avg. Referrer Power Rank
- 35.1
- Median Referrer Power Rank
- 32.6
- Referring Domains
- 167
- Linked Domains
- 39
Referring Domains by Power Rank
0–9 18
10–19 28
20–29 31
30–39 28
40–49 21
50–59 18
60–69 12
70–79 8
80–89 2
90–100 1
Total 167
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| github.com | 93.6 | #19 |
| cloudinary.com | 84.0 | #191 |
| vercel.com | 80.8 | #410 |
| jsdelivr.com | 78.6 | #629 |
| ycombinator.com | 78.0 | #705 |
| dev.to | 77.3 | #807 |
| smashingmagazine.com | 75.7 | #1,126 |
| prismic.io | 75.4 | #1,172 |
| telerik.com | 73.2 | #1,854 |
| freecodecamp.org | 72.1 | #2,287 |
Basic Information
- TLD
- .com
- Registration date
- 13 Feb 2020
- Last updated
- 24 Apr 2026
- Expires
- 13 Feb 2027 (100 days remaining)
- Domain statuses
- clientTransferProhibited
- Registry
- VeriSign Global Registry Services
- Registrar
- Name.com, Inc.
Subdomain
discord.blitzjs.comslack.blitzjs.comstore.blitzjs.com
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | blitzjs.com | 1800 | 216.150.16.129 |
| A | blitzjs.com | 1800 | 216.150.1.1 |
| MX | blitzjs.com | 60 | 10 in1-smtp.messagingengine.com |
| MX | blitzjs.com | 60 | 20 in2-smtp.messagingengine.com |
| NS | blitzjs.com | 86400 | ns1.vercel-dns.com |
| NS | blitzjs.com | 86400 | ns2.vercel-dns.com |
| SOA | blitzjs.com | 3600 | ns1.vercel-dns.com. hostmaster.nsone.net. 1654172013 43200 7200 1209600 600 |
| TXT | blitzjs.com | 60 | v=spf1 include:spf.messagingengine.com ?all |
| TXT | blitzjs.com | 60 | v=spf1 include:spfa.mailendo.com ~all |
| CAA | blitzjs.com | 60 | 0 issue "letsencrypt.org" |
| CAA | blitzjs.com | 60 | 0 issue "pki.goog" |
| CAA | blitzjs.com | 60 | 0 issue "sectigo.com" |
Email Authentication
- MX
- Valid
- SPF
- Configuration error
Multiple SPF records were found. Only one SPF policy should be published.
- DMARC
- Not configured
DMARC is not configured.
Some information is cached or comes from our own analysis, so it may not be current or complete. Our link analysis does not cover every link on the web. Metrics are based on our own methodology and should not be taken as definitive assessments of a domain’s or service’s quality or trustworthiness.