Skip to content

Hostname

feerik.com

Last fetched

feerik.com resolves to 188.114.96.3, announced in 188.114.96.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. feerik.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 · feerik.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/feerik.com

Resolution chain

IPv6 resolution

Attribution

oxeva

ORIGIN_AS

WHOIS identity

Registrar
iana:433
Registrant organisation
feerik
Contact emails
5h4bb7j22oxrxr3ei43m@z.o-w-o.info, 5s7m3mjsm1gbpcefp6s1@v.o-w-o.info, aqgq3us53wlp8wjhnbk7@k.o-w-o.info, csm66f8octudj3oliw5u@k.o-w-o.info, edldt2g8mp7g8tnt7dp1@r.o-w-o.info, k3cgwlgqnmlwfe1c2eq2@t.o-w-o.info

Subdomains

Subdomain
appsmith.feerik.com
banque-ssl.feerik.com
banque2.feerik.com
bar.feerik.com
bar2.feerik.com
blog.feerik.com
blogacclaim.feerik.com
blogde.feerik.com
blogold.feerik.com
blogtr.feerik.com
blogus.feerik.com
cn.feerik.com

Showing 12 of 41. View all subdomains →

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

  • terry.ns.cloudflare.com
  • walk.ns.cloudflare.com
  • ns1.reagi.com
  • ns2.reagi.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • apsmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • ip: 195.60.188.0/23
  • a: feerik.com
  • mx: feerik.com
  • include: _spf.google.com
  • include: spf.mailjet.com
  • ip: 158.255.65.29
  • ip: 94.23.26.138

Threat-feed evidence

History

Related pages

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