Skip to content

Hostname

computervision.com.bd

Last fetched

computervision.com.bd resolves to 203.18.159.112, announced in 203.18.158.0/23 by HOSTINGOXYGEN-AS-AP - Hosting Oxygen in BD. computervision.com.bd 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 · computervision.com.bdRouting diversity2.4/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.6/10canon.whisper.security/host/computervision.com.bd

Resolution chain

IPv6 resolution

No AAAA record for computervision.com.bd is recorded in WhisperGraph.

Attribution

oxygen

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for computervision.com.bd. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

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

  • dns1.bdnetservice.com
  • dns2.bdnetservice.com
  • ns3.bdnetservice.com
  • ns4.bdnetservice.com
  • earth.limda.net
  • mars.limda.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

MX records

  • computervision.com.bd

SPF policy

  • a: computervision.com.bd
  • mx: computervision.com.bd
  • ip: 203.18.159.112

Threat-feed evidence

History

Related pages

Pivot from computervision.com.bd 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: "computervision.com.bd"})-[: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.