Hostname
vedantaresources.com
Last fetched
vedantaresources.com resolves to 1 IPv4 address operated by GOOGLE-CLOUD-PLATFORM - Google LLC in IN. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
vedantaresources.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 |
|---|---|---|---|---|
| 34.93.59.18 | 34.93.48.0/20 | AS396982 | GOOGLE-CLOUD-PLATFORM - Google LLC | IN |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of vedantaresources.com owner
- Contact emails
- administrator@vedantaresources.com
- corporate-services@netnames.com
- 15541cb8-a883-4036-a437-516f22769501@identity-protect.org
- 3657c0bf-47be-41a4-bb27-05edc0e3b854@identity-protect.org
- 6bdbaec7-b275-4bf2-8342-fb408317a857@identity-protect.org
- 83780fce-05d8-4b78-b1f5-8fd84136cc08@identity-protect.org
- 95eea962-2cce-45c0-8520-d1d7af3540c4@identity-protect.org
- eab0e43e-9c3a-4669-ac9d-781860ecc356@identity-protect.org
Subdomains
7 observed subdomains of vedantaresources.com.
Web-graph footprint
Distinct hostnames that link to or from vedantaresources.com in the public web crawl.
188 sites link to this hostname.
39 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
3 SPF mechanisms authorising senders for vedantaresources.com.
| Mechanism | Target |
|---|---|
| SPF_A | london.vedantaresources.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_MX | vedantaresources.com |
Related pages
Pivot deeper into the graph from vedantaresources.com.
- IP · 34.93.59.18
- ASN · AS396982GOOGLE-CLOUD-PLATFORM - Google LLC
- Registrar · iana:468
- Country · IN
- Email · administrator@vedantaresources.com
- TLD · .com
- Browse hostnames · ve…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "vedantaresources.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.