Skip to content

Hostname

somosrex.com

Last fetched

somosrex.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. somosrex.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 · somosrex.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/somosrex.com

Resolution chain

No IPv4 resolution is recorded for somosrex.com in WhisperGraph.

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of somosrex.com owner
Contact emails
ofertasaqp@hotmail.com, 009e4ec3-a74d-49ec-a0d0-7f2259cef281@identity-protect.org, 1558db54-2169-42e7-8f27-9dedad9b744b@identity-protect.org, 173c560f-7e83-4439-a6a0-6941d11f0dd2@identity-protect.org, 17cd1f21-34e8-42d4-a870-1e15630541c4@identity-protect.org, 8ad5ef2c-3cd1-4aa2-bb28-02d7baed0d35@identity-protect.org, eac072f2-929c-4f4c-a037-6c206a968163@identity-protect.org, owner-10128189@somosrex.com.whoisprivacyservice.org, owner-3672645@somosrex.com.whoisprivacyservice.org, owner-8022027@somosrex.com.whoisprivacyservice.org

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

  • ns-159.awsdns-19.com
  • ns-656.awsdns-18.net
  • ns-1270.awsdns-30.org
  • ns-2040.awsdns-63.co.uk

MX records

  • somosrex-com.mail.protection.outlook.com

SPF policy

  • ip: 181.174.205.150/32
  • ip: 181.10.169.155/32
  • ip: 98.97.148.201/32
  • ip: 181.10.169.208/29
  • ip: 181.10.169.213/32
  • ip: 169.47.63.226/32
  • ip: 181.174.205.40/29
  • ip: 181.174.205.46/32

Threat-feed evidence

History

Related pages

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