Hostname
litigiumcapital.com
Last fetched
litigiumcapital.com resolves to 1 IPv4 address operated by AS44136 in SE. WHOIS lists iana:269 as the registrar.
Nutrition Label
Resolution chain
litigiumcapital.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 91.201.60.96 | 91.201.60.0/22 | AS44136 | — | SE |
WHOIS identity
- Registrar
- iana:269
- Organization
- c/o whoisproxy.com
- Contact emails
- tapishmehta@gmail.com
- 022089d3c944e59314e0349254b4807f9ac37d411049fca62c9b314498c02b04@litigiumcapital.com.whoisproxy.org
- 2e5fd9a530da78e4c380a998c04cd858ed6d9cb686cc85dc21f7cbe6540af275@litigiumcapital.com.whoisproxy.org
- 77c8c28e2b0afeed52a913970a3747a71a9b46eef94c250a52a907c96be9deb4@litigiumcapital.com.whoisproxy.org
- aa765a67809b4a0f8f47bcd2ee488ba28bc3080725c44eab46a3b3c78a985a8e@litigiumcapital.com.whoisproxy.org
- ab4408e545e210fb75f31a935289e630a32b772f0c618a2c946aca3697b273f7@litigiumcapital.com.whoisproxy.org
- ba48fe626272777412633b611ba7f46908a6e00bedaf565a4aeb47075033c502@litigiumcapital.com.whoisproxy.org
- ba76d05c2d87bc83145bfb533006f4ed19818f0d69d877aa14f0cffd9249e9be@litigiumcapital.com.whoisproxy.org
- d2bc664f07fb4aae1509a7ebf1ea3d2c1528bc45317df66fb84ead2c75909242@litigiumcapital.com.whoisproxy.org
- f2af547e4e681d85abeea63a3cc30552b862bbea50c30fdd4ae758279ffc7e73@litigiumcapital.com.whoisproxy.org
Subdomains
7 observed subdomains of litigiumcapital.com.
Web-graph footprint
Distinct hostnames that link to or from litigiumcapital.com in the public web crawl.
8 sites link to this hostname.
10 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
1 SPF mechanism authorising senders for litigiumcapital.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | spf.protection.outlook.com |
Related pages
Pivot deeper into the graph from litigiumcapital.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "litigiumcapital.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.