Skip to content

Hostname

excelityglobal.com

Last fetched

excelityglobal.com resolves to 20.119.16.26, announced in 20.64.0.0/10 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. excelityglobal.com 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 · excelityglobal.comRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/excelityglobal.com

Resolution chain

IPv6 resolution

No AAAA record for excelityglobal.com is recorded in WhisperGraph.

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:292
Registrant organisation
payfront technologies pte.
Contact emails
einstein.ece@gmail.com, bee.leong.lau@excelityglobal.com, vbadhniwalla@everstonecapital.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns1-08.azure-dns.com
  • ns4-08.azure-dns.info
  • ns2-08.azure-dns.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns3-08.azure-dns.org

MX records

  • mxa-0001b201.gslb.pphosted.com
  • mxb-0001b201.gslb.pphosted.com

SPF policy

  • ip: 67.231.152.177/32
  • ip: 208.84.65.220/32
  • a: excelityglobal.com
  • mx: excelityglobal.com
  • ip: 101.227.63.103
  • ip: 101.227.63.104
  • ip: 104.129.204.74
  • ip: 180.168.199.106
  • ip: 203.208.246.206
  • ip: 23.97.55.203
  • ip: 54.251.99.218

Threat-feed evidence

History

Related pages

Pivot from excelityglobal.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: "excelityglobal.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 20

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