lexblog.com
Its Domain Power Rank is relatively high.
- Global Rank
- #67,909
▲ 20,449
- Rank in TLD
- #30,139
▲ 8,247
- Referring Domains
- 1,481
▲ 25
- Avg. Referrer Power Rank
- 27.6
- Subdomains
- 79
- Domain age
- 22 yr 7 mo
Link Overview
- Avg. Referrer Power Rank
- 27.6
- Median Referrer Power Rank
- 24.7
- Referring Domains
- 1,481
- Linked Domains
- 2,929
Referring Domains by Power Rank
0–9 149
10–19 366
20–29 443
30–39 232
40–49 137
50–59 90
60–69 31
70–79 23
80–89 7
90–100 3
Total 1,481
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| wordpress.org | 93.7 | #18 |
| squarespace.com | 90.3 | #46 |
| t.me | 90.0 | #50 |
| weebly.com | 87.4 | #85 |
| nih.gov | 87.1 | #91 |
| stanford.edu | 83.3 | #237 |
| oup.com | 80.9 | #401 |
| berkeley.edu | 80.7 | #415 |
| constantcontact.com | 80.6 | #429 |
| cornell.edu | 80.6 | #424 |
Basic Information
- TLD
- .com
- Registration date
- 13 Mar 2004
- Last updated
- 14 Mar 2026
- Expires
- 13 Mar 2027 (128 days remaining)
- Domain statuses
- clientDeleteProhibited clientRenewProhibited clientTransferProhibited clientUpdateProhibited
- Registry
- VeriSign Global Registry Services
- Registrar
- GoDaddy.com, LLC
Subdomain
amlaw200.lexblog.comblogging.lexblog.comkevin.default.wp.corp.lexblog.comdonuts.lexblog.comdisabledworkerlaw.engage.lexblog.comnursinghomeabuseadvocate.engage.lexblog.comwormsandgermsblog.engage.lexblog.comfeeds.lexblog.comhosting.lexblog.combusinessofbenefits.ignite.lexblog.comcustomsandinternationaltradelaw.ignite.lexblog.comdashboardinsights.ignite.lexblog.comemergingcompanyexchange.ignite.lexblog.comemploymentlawlandscape.ignite.lexblog.comfloridacondohoalawblog.ignite.lexblog.comfoodlitigation.ignite.lexblog.comglobalpowerlaw.ignite.lexblog.comhealthcarelawtoday.ignite.lexblog.comipbulletin.ignite.lexblog.comipintelligencereport.ignite.lexblog.com
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | lexblog.com | 300 | 104.26.9.181 |
| A | lexblog.com | 300 | 104.26.8.181 |
| A | lexblog.com | 300 | 172.67.75.195 |
| AAAA | lexblog.com | 300 | 2606:4700:20::681a:8b5 |
| AAAA | lexblog.com | 300 | 2606:4700:20::681a:9b5 |
| AAAA | lexblog.com | 300 | 2606:4700:20::ac43:4bc3 |
| MX | lexblog.com | 300 | 10 aspmx.l.google.com |
| MX | lexblog.com | 300 | 20 alt1.aspmx.l.google.com |
| MX | lexblog.com | 300 | 20 alt2.aspmx.l.google.com |
| MX | lexblog.com | 300 | 30 aspmx2.googlemail.com |
| MX | lexblog.com | 300 | 30 aspmx3.googlemail.com |
| NS | lexblog.com | 86400 | betty.ns.cloudflare.com |
| NS | lexblog.com | 86400 | drew.ns.cloudflare.com |
| SOA | lexblog.com | 1800 | betty.ns.cloudflare.com. dns.cloudflare.com. 2419230644 10000 2400 604800 1800 |
| TXT | lexblog.com | 300 | anthropic-domain-verification-m2bwkt=qx26QJ9MeJrH4tFx36cNy9aL2 |
| TXT | lexblog.com | 300 | atlassian-domain-verification=ID68tM8cV21BdpnMyBa3BTTqB7g7PdUIZxnSxKAQhdIUqZAAPhUwig4F1nvbFGZf |
| TXT | lexblog.com | 300 | google-site-verification=GI2OEyxF1ddpeW_kn-KewIgnaSyrXZJvcxlsIwmK2DE |
| TXT | lexblog.com | 300 | google-site-verification=f5lJBAkp1uluA0YB23a4iwHwxg6mX318119TX-1PHYk |
| TXT | lexblog.com | 300 | status-page-domain-verification=6jglwscypyhp |
| TXT | lexblog.com | 300 | v=spf1 include:_spf.google.com include:servers.mcsv.net include:mail.zendesk.com include:stspg-customer.com a mx ~all |
| CAA | lexblog.com | 3600 | 0 issue "comodoca.com" |
| CAA | lexblog.com | 3600 | 0 issue "digicert.com; cansignhttpexchanges=yes" |
| CAA | lexblog.com | 3600 | 0 issue "letsencrypt.org" |
| CAA | lexblog.com | 3600 | 0 issue "pki.goog; cansignhttpexchanges=yes" |
| CAA | lexblog.com | 3600 | 0 issue "ssl.com" |
| CAA | lexblog.com | 3600 | 0 issuewild "comodoca.com" |
| CAA | lexblog.com | 3600 | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
| CAA | lexblog.com | 3600 | 0 issuewild "letsencrypt.org" |
| CAA | lexblog.com | 3600 | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
| CAA | lexblog.com | 3600 | 0 issuewild "ssl.com" |
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.