Skip to content

Hostname

homify.co.th

Last fetched

homify.co.th resolves to 108.128.131.199, announced in 108.128.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. homify.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 · homify.co.thRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/homify.co.th

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
registrar:thnic
Registrant organisation
asset consultant co., ltd. (บริษัท แอสเซ็ท คอนซัลแตนท์ จำกัด) represent of homify online gmbh & co. kg.

Subdomains

Subdomain
staging.homify.co.th
www.homify.co.th

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

Mail and authentication

Nameservers

  • ns-441.awsdns-55.com
  • ns-545.awsdns-04.net
  • 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-1077.awsdns-06.org
  • ns-1986.awsdns-56.co.uk

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

SPF policy

  • ip: 96.43.144.64/28
  • ip: 96.43.148.64/28
  • ip: 204.14.232.64/28
  • ip: 204.14.234.64/28
  • ip: 182.50.78.64/28
  • include: _spf.google.com
  • include: salesforce.com
  • include: _spf.makandra.de

Threat-feed evidence

History

Related pages

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