Skip to content

Hostname

mikomos.com

Last fetched

mikomos.com resolves to 104.21.5.119, announced in 104.21.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. mikomos.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 · mikomos.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/mikomos.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1479
Registrant organisation
domain administrator
Contact emails
pw-078bbeb17b58eef86a6df4af322fbd48@privacyguardian.org, pw-2c2e7ccd397224a31d0ebdd137001a01@privacyguardian.org, pw-4403bac3cf6da975bf7b255eeb5d0abf@privacyguardian.org, pw-a406815ee0a71163351cb1b4c4119a36@privacyguardian.org, pw-b347f52284f6894f8dce6d0eb6b3fc57@privacyguardian.org

Subdomains

Subdomain
5425e874270d.mikomos.com
dummyapp1.mikomos.com
mail.mikomos.com
www.mikomos.com

Showing 4 of 5. 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

Mail and authentication

Nameservers

  • kyle.ns.cloudflare.com
  • riya.ns.cloudflare.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

MX records

  • _dc-mx.5425e874270d.mikomos.com

SPF policy

  • include: smtp.wikiteq.com

Threat-feed evidence

History

Related pages

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