Skip to content

Hostname

spreadex.com

Last fetched

spreadex.com resolves to 75.2.58.125, announced in 75.2.48.0/20 by AMAZON-02 - Amazon.com, Inc. in US. spreadex.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 · spreadex.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/spreadex.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of spreadex.com owner
Contact emails
abuse@web.com, dataprotected@maskeddetails.com, infrastructure@spreadex.com, peter.miles@spreadex.com, 52245f2f-dda3-4366-82fe-8131312b4e92@identity-protect.org, d77c4e59-ad33-46b4-94e3-59b57a94a2ef@identity-protect.org, e0e53710-4f51-4275-bf87-4940d96e88c9@identity-protect.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-173.awsdns-21.com
  • ns-628.awsdns-14.net
  • ns-1091.awsdns-08.org
  • ns-1847.awsdns-38.co.uk
  • dns1.vietel.com.vn

MX records

  • eu-smtp-inbound-1.mimecast.com
  • eu-smtp-inbound-2.mimecast.com

SPF policy

  • ip: 192.254.125.237/32
  • include: amazonses.com
  • include: _netblocks.mimecast.com
  • include: eu._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • ip: 18.134.93.169
  • ip: 18.168.185.218
  • ip: 18.169.223.68
  • ip: 3.11.242.101
  • ip: 35.177.254.241
  • ip: 62.172.93.69

Threat-feed evidence

History

Related pages

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