Skip to content

Hostname

omega.com.do

Last fetched

omega.com.do resolves to 142.127.73.126, announced in 142.127.73.0/24 by BACOM - Bell Canada in CA. omega.com.do 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 · omega.com.doRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/omega.com.do

Resolution chain

IPv6 resolution

No AAAA record for omega.com.do is recorded in WhisperGraph.

Attribution

bell canada

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for omega.com.do. 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.midominio.do
  • dns2.midominio.do
  • dns3.midominio.do
  • dns4.midominio.do
  • 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

  • omega-com-do.p10.mxthunder.com
  • omega-com-do.p20.mxthunder.net
  • omega-com-do.p30.mxthunder.net
  • omega-com-do.p40.mxthunder.net

SPF policy

  • include: relay.dynu.com
  • a: relay.omega.com.do
  • ip: 142.127.73.126

Threat-feed evidence

History

Related pages

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