Skip to content

Hostname

okemedan.com

Last fetched

okemedan.com resolves to 103.112.245.10, announced in 103.112.245.0/24 by IDNIC-7ION-AS-ID - PT. Tujuh Ion Indonesia in ID. okemedan.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 · okemedan.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/okemedan.com

Resolution chain

IPv6 resolution

No AAAA record for okemedan.com is recorded in WhisperGraph.

Attribution

pt tujuh ion indonesia

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1675
Registrant organisation
domain data guard
Contact emails
ngjimmi@yahoo.com, noreply@domaindataguard.com

Subdomains

Subdomain
autodiscover.okemedan.com
cpanel.okemedan.com
cpcalendars.okemedan.com
cpcontacts.okemedan.com
mail.okemedan.com
webdisk.okemedan.com
webmail.okemedan.com
www.okemedan.com

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

  • dns1.indowebsite.net
  • dns2.indowebsite.net
  • dns3.indowebsite.net
  • dns4.indowebsite.net
  • 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

  • okemedan.com

SPF policy

  • a: okemedan.com
  • mx: okemedan.com
  • ip: 103.112.244.76
  • ip: 103.112.245.10
  • ip: 103.112.245.22
  • ip: 51.161.91.232
  • ip: 51.79.180.244

Threat-feed evidence

History

Related pages

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