Hostname
zuventus.com
Last fetched
zuventus.com resolves to 115.248.197.68, announced in 115.248.196.0/22 by RELIANCE-COMMUNICATIONS-IN - Reliance Communications Ltd.DAKC MUMBAI in IN. zuventus.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 115.248.197.68
115.248.196.0/22 · RELIANCE-COMMUNICATIONS-IN - Reliance Communications Ltd.DAKC MUMBAI · Chennai, IN
- 115.248.197.70
115.248.196.0/22 · RELIANCE-COMMUNICATIONS-IN - Reliance Communications Ltd.DAKC MUMBAI · Chennai, IN
- 220.225.32.193
220.225.32.0/23 · RELIANCE-COMMUNICATIONS-IN - Reliance Communications Ltd.DAKC MUMBAI · Chennai, IN
- 40.80.84.162
40.80.0.0/12 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Pune, IN
IPv6 resolution
No AAAA record for zuventus.com is recorded in WhisperGraph.
Attribution
Azure
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:303
- Registrant organisation
- domain admin
- Contact emails
- sanjay@emcure.co.in, contact@privacyprotect.org
Subdomains
Showing 11 of 11 subdomains (11 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns-cloud-d1.googledomains.com
- ns-cloud-d2.googledomains.com
- ns-cloud-d3.googledomains.com
- ns-cloud-d4.googledomains.com
MX records
- mx1.hc246-40.ap.iphmx.com
- mx2.hc246-40.ap.iphmx.com
- mxa-00ab2601.gslb.pphosted.com
- mxb-00ab2601.gslb.pphosted.com
SPF policy
- include: _u.zuventus.com._spf.smart.ondmarc.com
- ip: 206.1.14.29
Threat-feed evidence
History
Related pages
Pivot from zuventus.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "zuventus.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.