Skip to content

Hostname

fencapital.com

Last fetched

fencapital.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. fencapital.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 · fencapital.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/fencapital.com

Resolution chain

No IPv4 resolution is recorded for fencapital.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:1910
Registrant organisation
chen shaofeng
Contact emails
chensf777@gmail.com

Subdomains

Subdomain
australia.fencapital.com
ftp.fencapital.com
mail.fencapital.com
moontv.fencapital.com
pop.fencapital.com
smtp.fencapital.com
wildcard.fencapital.com
www.fencapital.com

Showing 8 of 8 subdomains (8 per page).

Mail and authentication

Nameservers

  • armando.ns.cloudflare.com
  • serenity.ns.cloudflare.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • ip: 51.254.104.0/24
  • ip: 45.150.109.0/24
  • ip: 167.148.115.0/24
  • ip: 185.28.119.0/24
  • ip: 213.109.147.0/24
  • ip: 45.143.166.0/24
  • ip: 185.102.173.0/24
  • ip: 188.64.184.0/24
  • ip: 81.31.213.0/24
  • ip: 91.236.230.0/24
  • ip: 173.239.238.0/24
  • ip: 45.66.249.0/24
  • ip: 212.8.251.0/24
  • ip: 146.19.254.0/24
  • ip: 98.159.35.0/24
  • ip: 45.123.43.0/24
  • ip: 85.239.53.0/24
  • ip: 173.244.60.0/24
  • ip: 62.106.66.0/24
  • ip: 94.23.77.0/24
  • ip: 146.255.85.0/24
  • ip: 64.64.97.0/24

Threat-feed evidence

History

Related pages

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