Skip to content

Hostname

mcfr.kz

Last fetched

mcfr.kz resolves to 91.201.214.226, announced in 91.201.228.0/22 by PSKZ-ALA - PS Internet Company LLP in KZ. mcfr.kz 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 · mcfr.kzRouting diversity1.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/mcfr.kz

Resolution chain

IPv6 resolution

No AAAA record for mcfr.kz is recorded in WhisperGraph.

Attribution

pskz ala ps

DNS_OPERATOR, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mcfr.kz. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
biot.mcfr.kz
buh.mcfr.kz
buhstudy.mcfr.kz
c-med.mcfr.kz
delopro.mcfr.kz
domain.mcfr.kz
e.mcfr.kz
edu.mcfr.kz
glavbukh.mcfr.kz
gos.mcfr.kz
gosbuh.mcfr.kz
goszakaz.mcfr.kz

Showing 12 of 154. 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

  • mcfr.kz
  • ns1.techdns.kz
  • ns2.techdns.kz

MX records

  • mailer.action.group
  • mailer2.action.group
  • mailer3.action.group
  • mx03.action.group
  • mx02.action.group
  • mx01.action.group

SPF policy

  • ip: 95.214.56.0/22
  • include: spf.unisender.com
  • include: action.group
  • include: action-media.ru
  • include: _spf.mail.ru
  • ip: 185.22.67.62
  • ip: 194.146.42.251
  • ip: 194.247.12.67
  • ip: 89.249.23.121
  • ip: 89.249.23.124
  • ip: 91.201.214.226

Threat-feed evidence

History

Related pages

Pivot from mcfr.kz 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: "mcfr.kz"})-[: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.