Skip to content

Hostname

thaifly.com

Last fetched

thaifly.com resolves to 103.40.116.141, announced in 103.40.116.0/24 by BANGMODENTERPRISE-TH - Bangmod Enterprise Co., Ltd. in TH. thaifly.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 · thaifly.comRouting diversity2.4/10Peering density5.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.0/10canon.whisper.security/host/thaifly.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Registrant organisation
whois agent
Contact emails
ccyrmrlg@whoisprivacyprotect.com, cxxmxyxr@whoisprivacyprotect.com, fkpdypgf@whoisprivacyprotect.com, kkclysby@whoisprivacyprotect.com, ryhcckqh@whoisprivacyprotect.com, tdhxrbddv@whoisprivacyprotect.com, tfqcknydj@whoisprivacyprotect.com

Subdomains

Subdomain
220-ns2.thaifly.com
220-ns3.thaifly.com
affiliate.thaifly.com
api.thaifly.com
assets.thaifly.com
autodiscover.thaifly.com
backend.thaifly.com
cpanel.thaifly.com
cpcalendars.thaifly.com
cpcontacts.thaifly.com
dashboard.thaifly.com
edu.thaifly.com

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

  • gemma.ns.cloudflare.com
  • jeremy.ns.cloudflare.com
  • dns1.name-services.com
  • dns2.name-services.com
  • dns3.name-services.com
  • dns4.name-services.com
  • dns5.name-services.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com

SPF policy

  • include: spf.mandrillapp.com
  • include: smtp.txmsv.com
  • include: servers.mcsv.net

Threat-feed evidence

History

Related pages

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