Skip to content

Hostname

kingsiam.com

Last fetched

kingsiam.com resolves to 172.96.191.202, announced in 172.96.190.0/23 by LEASEWEB-APAC-SIN-11 - LEASEWEB SINGAPORE PTE. LTD. in SG. kingsiam.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 · kingsiam.comRouting diversity1.5/10Peering density3.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/kingsiam.com

Resolution chain

IPv6 resolution

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

Attribution

leaseweb singapore pte

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
contact privacy inc. customer 0149606533
Contact emails
kingsiam.com@contactprivacy.com, 991f4e0dcdc4489c88502a28b2142642.protect@withheldforprivacy.com, krisdavut@intellinet.co.th

Subdomains

Subdomain
cpanel.kingsiam.com
cpcalendars.kingsiam.com
cpcontacts.kingsiam.com
mail.kingsiam.com
webdisk.kingsiam.com
webmail.kingsiam.com
www.kingsiam.com

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

  • ns5.hawkhost.com
  • ns6.hawkhost.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

MX records

  • kingsiam.com

SPF policy

  • include: _spf.arandomserver.com
  • a: kingsiam.com
  • mx: kingsiam.com
  • ip: 172.96.191.13

Threat-feed evidence

History

Related pages

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