Skip to content

Hostname

hamaly.qa

Last fetched

hamaly.qa resolves to 104.16.61.97, announced in 104.17.80.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. hamaly.qa 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 · hamaly.qaRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.5/10canon.whisper.security/host/hamaly.qa

Resolution chain

IPv6 resolution

No AAAA record for hamaly.qa is recorded in WhisperGraph.

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for hamaly.qa. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Mail and authentication

Nameservers

  • ns1.dns-parking.com
  • ns2.dns-parking.com
  • ns01.trademarkarea.com
  • ns02.trademarkarea.com
  • ns03.trademarkarea.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • smtp.google.com

SPF policy

  • include: spf.antispamcloud.com
  • include: _spf.google.com
  • ip: 69.16.203.179

Threat-feed evidence

History

Related pages

Pivot from hamaly.qa 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: "hamaly.qa"})-[: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.