Skip to content

Hostname

tips.co.th

Last fetched

tips.co.th resolves to 118.174.145.148, announced in 118.174.144.0/22 by TOT-LLI-AS-AP - TOT Public Company Limited in TH. tips.co.th 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 · tips.co.thRouting diversity1.5/10Peering density4.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/tips.co.th

Resolution chain

IPv6 resolution

No AAAA record for tips.co.th is recorded in WhisperGraph.

Attribution

royal thai armed force headquarters

ORIGIN_AS

WHOIS identity

Registrar
registrar:thnic
Registrant organisation
tips co., ltd. (บริษัท ที ไอ พี เอส จำกัด)

Subdomains

Subdomain
approval.tips.co.th
intranet.tips.co.th
jabber.tips.co.th
mailgw1.tips.co.th
mailgw2.tips.co.th
websrv1.tips.co.th
websrv2.tips.co.th
www.tips.co.th

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

  • ns1.idc.cattelecom.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
  • myna.cat.net.th

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • mailgw1.tips.co.th

SPF policy

  • include: _spf.google.com
  • ip: 118.174.145.149
  • ip: 122.154.125.91

Threat-feed evidence

History

Related pages

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