Skip to content

Hostname

qp.qa

Last fetched

qp.qa resolves to 104.20.2.74, announced in 104.20.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. qp.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 · qp.qaRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.8/10canon.whisper.security/host/qp.qa

Resolution chain

IPv6 resolution

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

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
registrar:ooredoo qsc
Registrant organisation
iyad saad

Subdomains

Subdomain
a-sacdp.qp.qa
adp-m.qp.qa
adp.qp.qa
amd.qp.qa
appst.qp.qa
assaiprd.qp.qa
bdp-m.qp.qa
bv.qp.qa
bw-dev1.qp.qa
careers-test.qp.qa
careers.qp.qa
cdp-m.qp.qa

Showing 12 of 97. View all subdomains →

Mail and authentication

Nameservers

  • 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
  • ns0.qatarenergy.qa
  • ns1.qatarenergy.qa
  • ns2.qatarenergy.qa
  • ns3.qatarenergy.qa
  • ns4.qatarenergy.qa
  • hostmaster.qp.qa
  • dkn-dct-g04-dmz-gtm-1.security.qp.qa

MX records

  • mailgw1.qp.com.qa
  • mailgw2.qp.com.qa
  • mailgw3.qp.com.qa

SPF policy

  • ip: 185.2.244.22/32
  • ip: 185.2.246.22/32
  • ip: 185.2.244.23/32
  • a: mailgw1.qp.com.qa
  • a: mailgw2.qp.com.qa
  • a: mailgw3.qp.com.qa

Threat-feed evidence

History

Related pages

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