Skip to content

Hostname

mkaku.org

Last fetched

mkaku.org resolves to 69.12.78.98, announced in 69.12.78.0/24 by AS-COLOCROSSING - HostPapa in US. mkaku.org 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 · mkaku.orgRouting diversity1.5/10Peering density6.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/mkaku.org

Resolution chain

IPv6 resolution

No AAAA record for mkaku.org is recorded in WhisperGraph.

Attribution

hostpapa

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
phys. dept., c.u.n.y.
Contact emails
kt3qv8az725@networksolutionsprivateregistration.com, mkaku@aol.com, n76rw8a58j5@networksolutionsprivateregistration.com, nq2sq55x889@networksolutionsprivateregistration.com, nv92k6k62tz@networksolutionsprivateregistration.com, r64kr8tu5vd@networksolutionsprivateregistration.com, wa45d2a65jm@networksolutionsprivateregistration.com, y74t285c8u9@networksolutionsprivateregistration.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

  • ns1.hostname.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
  • ns1.mkaku.org
  • ns2.mkaku.org

MX records

  • mail.mkaku.org

SPF policy

  • a: mkaku.org
  • mx: mkaku.org
  • ip: 67.210.105.198
  • ip: 69.12.78.98

Threat-feed evidence

History

Related pages

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