Skip to content

Hostname

xcellhost.in

Last fetched

xcellhost.in is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. xcellhost.in is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · xcellhost.inRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.3/10canon.whisper.security/host/xcellhost.in

Resolution chain

No IPv4 resolution is recorded for xcellhost.in in WhisperGraph.

IPv6 resolution

No AAAA record for xcellhost.in is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:801217
Registrant organisation
mr. samir jhaveri
Contact emails
samir@xcellhost.in

Subdomains

Subdomain
220-racknap.xcellhost.in
bizmail.xcellhost.in
bizmail1.xcellhost.in
blog.xcellhost.in
blrrelay.xcellhost.in
bss.xcellhost.in
call2connect.xcellhost.in
cc.xcellhost.in
demo.xcellhost.in
domainadmin.xcellhost.in
emarketing.xcellhost.in
maildefence01.xcellhost.in

Showing 12 of 46. View all subdomains →

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

  • ns1-03.azure-dns.com
  • xcellhost.earth.orderbox-dns.com
  • xcellhost.mars.orderbox-dns.com
  • xcellhost.mercury.orderbox-dns.com
  • xcellhost.venus.orderbox-dns.com
  • ns4-03.azure-dns.info
  • ns2-03.azure-dns.net
  • ns3-03.azure-dns.org

MX records

  • xcellhost-in.mail.protection.outlook.com

SPF policy

  • include: spf.mailjet.com
  • a: mx02.officeinfra.com
  • include: spf.protection.outlook.com
  • a: xcellhost.in
  • mx: xcellhost.in
  • include: spf.exclaimer.net
  • ip: 103.29.235.87

Threat-feed evidence

History

Related pages

Pivot from xcellhost.in 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: "xcellhost.in"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.