Skip to content

Hostname

j-cup.org

Last fetched

j-cup.org resolves to 103.247.10.177, announced in 103.247.10.0/24 by CRI-AS-AP - CV. Rumahweb Indonesia in ID. j-cup.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 · j-cup.orgRouting diversity1.5/10Peering density4.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/j-cup.org

Resolution chain

IPv6 resolution

Attribution

rumahweb

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1675
Registrant organisation
whois privacy protection service by onamae.com
Contact emails
nagoyakawa.inc@gmail.com, proxy@whoisprotectservice.com

Subdomains

Subdomain
autodiscover.j-cup.org
cpanel.j-cup.org
cpcalendars.j-cup.org
cpcontacts.j-cup.org
ipv6.j-cup.org
mail.j-cup.org
webdisk.j-cup.org
webmail.j-cup.org
www.j-cup.org

Showing 9 of 9 subdomains (9 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

  • ns1.rumahweb.com
  • ns2.rumahweb.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
  • ns3.rumahweb.net
  • ns4.rumahweb.net

MX records

  • j-cup.org

SPF policy

  • a: j-cup.org
  • mx: j-cup.org
  • ip: 103.247.10.175
  • ip: 103.247.9.28
  • ip: 103.253.212.124
  • ip: 103.253.212.126
  • ip: 203.175.8.156
  • ip: 203.175.8.158
  • ip: 203.175.9.92
  • ip: 203.175.9.93

Threat-feed evidence

History

Related pages

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