Skip to content

Hostname

m-uroko.com

Last fetched

m-uroko.com resolves to 104.21.34.133, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. m-uroko.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 · m-uroko.comRouting diversity3.0/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.3/10canon.whisper.security/host/m-uroko.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · MAIL_RECEIVER, ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:49
Registrant organisation
whois privacy protection service by onamae.com
Contact emails
admin@onamae.com, proxy@whoisprotectservice.com, program.swordfish@gmail.com

Subdomains

Subdomain
info.m-uroko.com
mta-sts.m-uroko.com
www.m-uroko.com

Showing 3 of 3 subdomains (3 per page).

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

  • aarav.ns.cloudflare.com
  • paityn.ns.cloudflare.com
  • dns1.onamae-expired.com
  • dns2.onamae-expired.com
  • ns1.gm111.parklogic.com
  • ns2.gm111.parklogic.com
  • ns1.xserver.jp
  • ns2.xserver.jp
  • ns3.xserver.jp
  • ns4.xserver.jp
  • ns5.xserver.jp
  • 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

  • m-uroko.com

SPF policy

  • a: m-uroko.com
  • mx: m-uroko.com
  • include: spf.sender.xserver.jp
  • a: sv1210.xserver.jp

Threat-feed evidence

History

Related pages

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