Skip to content

Hostname

rexmarine.com

Last fetched

rexmarine.com resolves to 34.232.201.64, announced in 34.224.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. rexmarine.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 · rexmarine.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/rexmarine.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
aravidis@me.com, ax3uu2vn7b9@networksolutionsprivateregistration.com, d89h764r48u@networksolutionsprivateregistration.com, ew7ht42m2sg@networksolutionsprivateregistration.com, internet@actweb.com, mb2uy6uk6fr@networksolutionsprivateregistration.com, qf2tu7g9896@networksolutionsprivateregistration.com, qp4z69as53p@networksolutionsprivateregistration.com, ted@nps-international.com, ve7k62r49b8@networksolutionsprivateregistration.com

Subdomains

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

Mail and authentication

Nameservers

  • ns89.worldnic.com
  • ns90.worldnic.com

MX records

  • rexmarine-com.inbound.emailservice.cc
  • rexmarine-com.inbound.emailservice.co
  • rexmarine-com.inbound.emailservice.io

SPF policy

  • include: amazonses.com
  • include: spf.protection.outlook.com
  • include: spf.securence.com
  • include: _spf_cd.spamtitan.com
  • include: spf.us.emailservice.io

Threat-feed evidence

History

Related pages

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