Skip to content

Hostname

journalarta.com

Last fetched

journalarta.com resolves to 103.103.145.85, announced in 103.103.145.0/24 by ARTAMEDIANET-AS-ID - PT. ARTAMEDIA CITRA TELEMATIKA INDONESIA in ID. journalarta.com is listed by 1 threat feed; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

Listed by 1 threat feed. Advisory: url-scoped-listing.

Threat feeds listing this
1
Verdict coverage
known-clean
First seen on a feed
Wed, 26 Aug 2026 14:45:24 GMT
Last seen on a feed
Mon, 14 Sep 2026 19:54:16 GMT

Nutrition Label

WHISPER CANON · journalarta.comRouting diversity2.4/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/journalarta.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · MAIL_RECEIVER, ORIGIN_AS, CDN

WHOIS identity

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

Subdomains

Subdomain
autodiscover.journalarta.com
automation.journalarta.com
cpanel.journalarta.com
cpcalendars.journalarta.com
cpcontacts.journalarta.com
mail.journalarta.com
news.journalarta.com
webdisk.journalarta.com
webmail.journalarta.com
www.journalarta.com

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

  • srvns1.artamedianet.com
  • srvns2.artamedianet.com
  • jason.ns.cloudflare.com
  • nora.ns.cloudflare.com

MX records

  • journalarta.com
  • mail.journalarta.com
  • _dc-mx.9370c6367d1c.journalarta.com

SPF policy

  • a: journalarta.com
  • mx: journalarta.com
  • ip: 103.103.145.210
  • ip: 103.103.145.85
  • ip: 103.103.145.94
  • ip: 103.103.146.37
  • ip: 103.103.146.39
  • ip: 103.103.147.138
  • ip: 103.103.147.139

Threat-feed evidence

History

Related pages

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