🌐 https://www.courtlistener.com/api/rest/v4/sources/
URL
· host
www.courtlistener.com
· threat 0.50 (HIGH)
· Court Cases First seen 2026-08-06 13:13:25 · last seen 2026-08-06 13:13:25
🔄 Pivot:📁 Court Cases
Threat score
0.50
MEDIUM
Sightings
1
1 sources
Subdomains (local)
0
from indicators
Related IPs
4
A/AAAA records
DNS records (local)
0
0 types
Reporting sources
1
0 enrichments
📡 Reporting-source breakdown
1
1 total source links on this indicator.
🏷 Tag breakdown (domain family)
1
1
1
📈 DNS record-type counts
No data.
📅 First-seen timeline (family)
1
🏷 WHOIS / Registration (local cache)
No cached WHOIS for www.courtlistener.com. Resolve & cache.
📡 DNS Records
Live (DNS-over-HTTPS · optional augmentation)
| Type | Value | TTL |
|---|---|---|
| A | courtlistener.com. |
21463 |
| A | 18.238.109.34 |
60 |
| A | 18.238.109.114 |
60 |
| A | 18.238.109.91 |
60 |
| A | 18.238.109.56 |
60 |
| AAAA | courtlistener.com. |
21463 |
| MX | courtlistener.com. |
21449 |
| MX | 10 alt4.aspmx.l.google.com. |
300 |
| MX | 1 aspmx.l.google.com. |
300 |
| MX | 5 alt1.aspmx.l.google.com. |
300 |
| MX | 5 alt2.aspmx.l.google.com. |
300 |
| MX | 10 alt3.aspmx.l.google.com. |
300 |
| NS | courtlistener.com. |
21585 |
| NS | ns-1405.awsdns-47.org. |
21600 |
| NS | ns-432.awsdns-54.com. |
21600 |
| NS | ns-791.awsdns-34.net. |
21600 |
| NS | ns-2043.awsdns-63.co.uk. |
21600 |
| TXT | courtlistener.com. |
21342 |
| TXT | google-site-verification=E9l8i1T-eezoNaA3SRmfkIs8TflGMgaDDh6z5TokUno |
300 |
| TXT | brave-ledger-verification=c9a3bd30e22e16786ca2a3e4971a1b521577e2e956c846ff30aa37c1939a1f53 |
300 |
| TXT | v=spf1 a include:_spf.google.com ~all |
300 |
| CNAME | courtlistener.com. |
21589 |
🖥 Related IPs (4)
Resolved from local A/AAAA records (augmented with live DoH when reachable). Each pivots to its IP dossier.
🌐 Subdomains — local intel (0)
No subdomains of www.courtlistener.com in local intel. Check crt.sh ↗
📡 Reporting Sources (1)
CourtListener REST API | Court Cases |
🌐 Same-ASN domains (0)
No ASN linkage in local intel.
🔍 OSINT pivots — external lookups
🔗 Internal pivots & actions
📁 Case Management
Every panel resolves local-first: threat, category, first-seen & sightings from
indicators; DNS from dns_records; WHOIS from whois_cache; subdomains via bounded suffix match on indicators; related IPs from A/AAAA records; tags, reporting sources and the link graph from the local relations. Live OTX pulses and DNS-over-HTTPS are optional augmentation and their absence never blanks the dossier.
Workstation · Copilot · AI Skills · Automation · Playbooks · Lookups · Docs · Reports
🤖 AI Copilot
⚡ AI Skills
🔍 Lookup & Enrich
📚 Docs & Reports
💡 Recommendations
- Audit DNS to build passive history
- Pivot resolved IPs to their dossiers
- Report phishing to registrar/host