lisk.com
- Domain Power global ranking: #77,977
Its Domain Power Rank is relatively high. This domain was registered at least 20 years ago. Links from multiple referring domains appear in the observed data.
- Global Rank
- #77,977
▲ 905
- Rank in TLD
- #34,490
▲ 25
- Referring Domains
- 425
▲ 39
- Avg. Referrer Power Rank
- 32.1
- Subdomains
- 33
- Domain age
- 27 yr 9 mo
Link Overview
- Avg. Referrer Power Rank
- 32.1
- Median Referrer Power Rank
- 30.1
- Referring Domains
- 425
- Linked Domains
- 234
Referring Domains by Power Rank
0–9 50
10–19 78
20–29 81
30–39 76
40–49 56
50–59 51
60–69 17
70–79 10
80–89 4
90–100 2
Total 425
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| google.com | 99.8 | #1 |
| github.com | 93.6 | #19 |
| bit.ly | 88.4 | #67 |
| substack.com | 84.4 | #173 |
| prnewswire.com | 82.7 | #272 |
| dribbble.com | 81.8 | #326 |
| dev.to | 77.3 | #807 |
| luma.com | 75.2 | #1,222 |
| beehiiv.com | 75.1 | #1,264 |
| tradingview.com | 73.7 | #1,645 |
Basic Information
- TLD
- .com
- Registration date
- 10 Jan 1999
- Last updated
- 26 Oct 2026
- Expires
- 10 Jan 2030 (1,162 days remaining)
- Domain statuses
- clientUpdateProhibited clientTransferProhibited clientDeleteProhibited serverUpdateProhibited serverTransferProhibited serverDeleteProhibited
- Registry
- VeriSign Global Registry Services
- Registrar
- Markmonitor Inc.
Subdomain
accelerator.lisk.comrpc.api.lisk.comapp.lisk.combetanet-faucet.lisk.combetanet-service.lisk.comblockscout.lisk.comwww.blockscout.lisk.comblog.lisk.combridge.lisk.comdemo.lisk.comdev.lisk.comdocs.lisk.comdocumentation.lisk.comexplorer.lisk.comforum.lisk.comgelato-bridge.lisk.comhodlerdrop.lisk.comhub.lisk.comlegacy-explorer.lisk.commagazine.lisk.com
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | lisk.com | 300 | 184.169.135.34 |
| A | lisk.com | 300 | 52.8.178.132 |
| MX | lisk.com | 3600 | 1 aspmx.l.google.com |
| MX | lisk.com | 3600 | 10 alt3.aspmx.l.google.com |
| MX | lisk.com | 3600 | 10 alt4.aspmx.l.google.com |
| MX | lisk.com | 3600 | 5 alt1.aspmx.l.google.com |
| MX | lisk.com | 3600 | 5 alt2.aspmx.l.google.com |
| NS | lisk.com | 172800 | ns-1376.awsdns-44.org |
| NS | lisk.com | 172800 | ns-1578.awsdns-05.co.uk |
| NS | lisk.com | 172800 | ns-472.awsdns-59.com |
| NS | lisk.com | 172800 | ns-793.awsdns-35.net |
| SOA | lisk.com | 900 | ns-1376.awsdns-44.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 |
| TXT | lisk.com | 3600 | 8a71af6c-d6bb-45ff-859a-71cdd5bff65f=eef6947d50df6358cdbd816091ba4c2ee96bb92b88299c05a6943fc6dd57a88d |
| TXT | lisk.com | 3600 | ahrefs-site-verification_985033cda3d106751c53e2080a2cb5bd5335f326e398ab02ce67bce4e460f6e4 |
| TXT | lisk.com | 3600 | google-site-verification=7lx0ha911xtP2hgnQIfqtLAHF8ORDv7r56QDRsppc5Q |
| TXT | lisk.com | 3600 | google-site-verification=E2mvbgZBq6003Ansu3qb2O9dZHG8gyUb06JJYoI5cnk |
| TXT | lisk.com | 3600 | google-site-verification=RbAwapp2gNSKKE7u_h12GwGulcEndY5DW1bYm6b3lZo |
| TXT | lisk.com | 3600 | google-site-verification=nEAd5j8chY5-0iMNPudOR2P62y8jlM0DOHgSW8EXIh4 |
| TXT | lisk.com | 3600 | have-i-been-pwned-verification=c46286cb967d56bae17a52c33721145f |
| TXT | lisk.com | 3600 | langdock-verify=7Bw5vseVHb0ljXMw0FH0tHe1GxfFfv5or6KpPGYk3XU |
| TXT | lisk.com | 3600 | v=spf1 include:_spf.google.com -all |
| CAA | lisk.com | 300 | 0 iodef "mailto:sysops@lightcurve.io" |
| CAA | lisk.com | 300 | 0 issue "amazon.com" |
| CAA | lisk.com | 300 | 0 issue "letsencrypt.org" |
| CAA | lisk.com | 300 | 0 issue "pki.goog" |
| CAA | lisk.com | 300 | 0 issue "sectigo.com" |
| CAA | lisk.com | 300 | 0 issue "ssl.com" |
| CAA | lisk.com | 300 | 0 issuewild "amazon.com" |
| CAA | lisk.com | 300 | 0 issuewild "letsencrypt.org" |
Email Authentication
- MX
- Valid
- SPF
- Valid
- DMARC
- Valid
DMARC is set to p=reject, asking receiving servers to reject messages that fail authentication.
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.