Skip to content

Hostname

tiketkai.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1675
Registrant organisation
ibnu sunanto
Contact emails
ibnusunanto@gmail.com, dataprotected@undisclosed.id

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • carlos.ns.cloudflare.com
  • mira.ns.cloudflare.com
  • ns0.dnsmadeeasy.com
  • ns1.dnsmadeeasy.com
  • ns2.dnsmadeeasy.com
  • ns3.dnsmadeeasy.com
  • ns4.dnsmadeeasy.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

SPF policy

  • ip: 118.97.232.0/29
  • ip: 180.250.248.129/28
  • ip: 202.43.173.232/29
  • ip: 202.152.59.248/29
  • ip: 103.247.10.226
  • ip: 103.247.9.129
  • ip: 103.253.113.101
  • ip: 103.253.113.102
  • ip: 103.253.113.103
  • ip: 103.82.240.160
  • ip: 103.82.240.8
  • ip: 173.214.191.138
  • ip: 173.214.191.139
  • ip: 35.240.152.180

Threat-feed evidence

History

Related pages

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