Skip to content

Hostname

ohmymag.com

Last fetched

ohmymag.com resolves to 185.151.190.11, announced in 185.151.188.0/22 by ODISO-AS - CYLLENE ITS SAS in FR. ohmymag.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 · ohmymag.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/ohmymag.com

Resolution chain

IPv6 resolution

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

Attribution

cyllene its

ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
amatech sc
Contact emails
182d1fd1b5d00bcd52ba0ef039a04521-4131452@contact.gandi.net, 346abc2982c83a540f37b7562a200ba1-4131452@contact.gandi.net, 358cce3aae29aae3ff6400c3a22778f5-4131452@contact.gandi.net, 5c61484fdf8d9888008b492217cd1e9b-4131452@contact.gandi.net, 8ced495f6297d0cabda725756b10780b-4131452@contact.gandi.net, 92d1d98075f7fbc5942d1c6b087bde37-4131452@contact.gandi.net, a6b0036a2ab40d9c4e6bedf60f20b98a-4131452@contact.gandi.net, b1af24f65575f0d8e8c114c6467f2407-712511@contact.gandi.net, b36aa0c2aaa365f55af8e2f83e3507b1-4131452@contact.gandi.net, da07b8f208b7ea36c6187558e6428ffa-4131452@contact.gandi.net

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

  • ns2.cetsi.eu
  • ns1.cetsi.fr
  • ns3.cetsi.info
  • ns-139-b.gandi.net
  • ns-187-c.gandi.net
  • ns-247-a.gandi.net

MX records

  • smtp.google.com

SPF policy

  • include: _spf.google.com
  • include: cerise.media

Threat-feed evidence

History

Related pages

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