Skip to content

Hostname

alphaomega.ms

Last fetched

alphaomega.ms resolves to 109.234.166.250, announced in 109.234.164.0/22 by O2SWITCH - O2SWITCH SAS in FR. alphaomega.ms 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 · alphaomega.msRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/alphaomega.ms

Resolution chain

IPv6 resolution

No AAAA record for alphaomega.ms is recorded in WhisperGraph.

Attribution

o2switch

ORIGIN_AS

WHOIS identity

Registrar
registrar:gandi sas
Registrant organisation
redacted | eu registrar

Subdomains

Subdomain
dev-odoo.alphaomega.ms
preprod-pro.alphaomega.ms
preprod.alphaomega.ms
pro.alphaomega.ms
ps8.alphaomega.ms
www.alphaomega.ms

Showing 6 of 6 subdomains (6 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

Sample outbound links

Mail and authentication

Nameservers

  • ns-100-c.gandi.net
  • ns-119-b.gandi.net
  • ns-148-a.gandi.net
  • ns1.gandi.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • include: _mailcust.gandi.net

Threat-feed evidence

History

Related pages

Pivot from alphaomega.ms 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: "alphaomega.ms"})-[: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.