Skip to content

Hostname

fentrend.com

Last fetched

fentrend.com resolves to 67.223.118.19, announced in 67.223.118.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. fentrend.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 · fentrend.comRouting diversity1.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.6/10canon.whisper.security/host/fentrend.com

Resolution chain

IPv6 resolution

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

Attribution

namecheap

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
andy huh
Contact emails
andy@fentrend.com, andyhuh@gmail.com, bdyvfldnx@whoisprivacyprotect.com, 0d75d3ca61184e6a8a8dccc1b420064f.protect@withheldforprivacy.com, pw-6a3b9b31fd88fce5fb475b31d0602d42@privacyguardian.org, pw-e3a985cb178b2259811c15f12988337d@privacyguardian.org

Subdomains

Subdomain
www.fentrend.com

Showing 1 of 1 subdomain (1 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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • dns1.namecheaphosting.com
  • dns2.namecheaphosting.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • f.root-servers.net
  • h.root-servers.net
  • k.root-servers.net
  • m.root-servers.net

MX records

  • mx1-hosting.jellyfish.systems
  • mx2-hosting.jellyfish.systems
  • mx3-hosting.jellyfish.systems

SPF policy

  • a: fentrend.com
  • mx: fentrend.com
  • include: spf.web-hosting.com
  • ip: 66.29.137.231

Threat-feed evidence

History

Related pages

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