Skip to content

Hostname

quick.co.id

Last fetched

quick.co.id resolves to 103.44.27.149, announced in 103.44.27.0/24 by IDNIC-BIZNETGIO-AS-ID - PT Biznet Gio Nusantara in ID. quick.co.id 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 · quick.co.idRouting diversity1.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/quick.co.id

Resolution chain

IPv6 resolution

No AAAA record for quick.co.id is recorded in WhisperGraph.

Attribution

pt biznet gio nusantara

ORIGIN_AS

WHOIS identity

Registrar
iana:1
Registrant organisation
cv. karya hidup sentosa
Contact emails
it.sec1@quick.co.id

Subdomains

Subdomain
apps.quick.co.id
appsdev.quick.co.id
cpanel.quick.co.id
dinas.quick.co.id
dl.quick.co.id
localhost.quick.co.id
m.quick.co.id
mail.quick.co.id
mx.quick.co.id
order.quick.co.id
recruit.quick.co.id
svr0.quick.co.id

Showing 12 of 22. View all subdomains →

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

  • jktns1.biz.net.id
  • ns1.biz.net.id
  • ns2.biz.net.id
  • ns3.biz.net.id
  • ns4.biz.net.id
  • 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

  • mx.quick.co.id

SPF policy

  • ip: 117.102.98.0/24
  • a: quick.co.id
  • mx: quick.co.id
  • include: smtp.biz.net.id
  • ip: 103.44.27.149

Threat-feed evidence

History

Related pages

Pivot from quick.co.id 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: "quick.co.id"})-[: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.