Skip to content

Hostname

seachefs.com

Last fetched

seachefs.com resolves to 52.29.127.0, announced in 52.29.0.0/16 by AMAZON-02 - Amazon.com, Inc. in DE. seachefs.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 · seachefs.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/seachefs.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1408
Registrant organisation
hans-peter fischer
Contact emails
contact@seachefs.com, licensing@seachefs.com

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

  • kyrie.ns.cloudflare.com
  • tiffany.ns.cloudflare.com
  • 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

MX records

  • seachefs-com.mail.protection.outlook.com

SPF policy

  • include: amazonses.com
  • include: spf.emailsignatures365.com
  • include: spf_c.oraclecloud.com
  • include: spf.protection.outlook.com
  • a: seachefs.com
  • mx: seachefs.com
  • ip: 149.72.190.99
  • ip: 149.72.246.141
  • ip: 160.34.223.21
  • ip: 168.128.13.150
  • ip: 213.61.245.66
  • ip: 217.110.247.190

Threat-feed evidence

History

Related pages

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