Skip to content

Hostname

correct.go.th

Last fetched

correct.go.th resolves to 203.147.24.123, announced in 203.147.138.0/24 by JASTEL-NETWORK-IDC - JasTel Network in TH. correct.go.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 · correct.go.thRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/correct.go.th

Resolution chain

IPv6 resolution

No AAAA record for correct.go.th is recorded in WhisperGraph.

Attribution

jastel idc

ORIGIN_AS

WHOIS identity

Registrar
registrar:t.h.nic co., ltd.

Subdomains

Subdomain
bp.correct.go.th
bpo.correct.go.th
br.correct.go.th
catalog.correct.go.th
cc.correct.go.th
en.correct.go.th
fd.correct.go.th
gw.correct.go.th
lad.correct.go.th
logcenter.correct.go.th
mail.correct.go.th
mail2.correct.go.th

Showing 12 of 23. 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

Mail and authentication

Nameservers

  • ns.ji-net.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
  • ns.ji-net.co.th
  • ns2.ji-net.co.th

MX records

  • antispam1.thaicloudsolutions.com
  • antispam2.thaicloudsolutions.com
  • antispamccs.thaicloudsolutions.com

SPF policy

  • include: _spf.thaicloudsolutions.com
  • a: mail.correct.go.th

Threat-feed evidence

History

Related pages

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