Skip to content

Hostname

strat7.com

Last fetched

strat7.com resolves to 13.134.170.189, announced in 13.134.0.0/15 by AMAZON-02 - Amazon.com, Inc. in GB. strat7.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 · strat7.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/strat7.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
recopat gmbh & co. kg
Contact emails
bengt.wessling@gmx.net, 08a42dba-98bd-47a0-bab7-49eff4e9f3d5@identity-protect.org, a4cd1fc1-a9f6-488d-ad22-bac949a4ff44@identity-protect.org, d61d77f3-e7dd-487c-8795-7a27fab759a4@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-211.awsdns-26.com
  • ns-541.awsdns-03.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
  • ns-1408.awsdns-48.org
  • ns-1605.awsdns-08.co.uk

MX records

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

SPF policy

  • include: amazonses.com
  • include: eu._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • include: 9492080.spf05.hubspotemail.net
  • include: servers.mcsv.net
  • include: spf.uk.signature365.net

Threat-feed evidence

History

Related pages

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