Skip to content

Hostname

qdc.com.qa

Last fetched

qdc.com.qa resolves to 13.107.226.45, announced in 13.104.0.0/14 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in CA. qdc.com.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 · qdc.com.qaRouting diversity2.4/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.6/10canon.whisper.security/host/qdc.com.qa

Resolution chain

IPv6 resolution

No AAAA record for qdc.com.qa is recorded in WhisperGraph.

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for qdc.com.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.

Subdomains

Showing 1 of 1 subdomain (1 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.

Mail and authentication

Nameservers

  • a1-157.akam.net
  • a14-64.akam.net
  • a22-65.akam.net
  • a4-66.akam.net
  • a5-67.akam.net
  • a9-64.akam.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

MX records

  • mx1.qatarairways.com.qa
  • mx2.qatarairways.com.qa
  • mx4.qatarairways.com.qa
  • mx5.qatarairways.com.qa
  • vmx1.qatarairways.com.qa
  • vmx2.qatarairways.com.qa
  • vmx7.qatarairways.com.qa
  • vmx8.qatarairways.com.qa

SPF policy

  • include: _u.qdc.com.qa._spf.smart.ondmarc.com

Threat-feed evidence

History

Related pages

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