Skip to content

Hostname

phcc.gov.qa

Last fetched

phcc.gov.qa resolves to 104.16.4.14, announced in 104.16.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. phcc.gov.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 · phcc.gov.qaRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/phcc.gov.qa

Resolution chain

IPv6 resolution

No AAAA record for phcc.gov.qa is recorded in WhisperGraph.

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

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

Subdomain
access.phcc.gov.qa
app-aiapp-cb-prd-sc.phcc.gov.qa
autodiscover.phcc.gov.qa
careers.phcc.gov.qa
cisapp.phcc.gov.qa
datixweb.phcc.gov.qa
e-library.phcc.gov.qa
engage.phcc.gov.qa
mail.phcc.gov.qa
ns1.phcc.gov.qa
ns2.phcc.gov.qa
ns3.phcc.gov.qa

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

  • ns1-04.azure-dns.com
  • ns4-04.azure-dns.info
  • ns2-04.azure-dns.net
  • ns3-04.azure-dns.org

MX records

  • smtp1.phcc.gov.qa
  • smtp2.phcc.gov.qa
  • df-nu4a-g8rhv-jl689-g9c89-ruukm-t7dhr.in.tmes.trendmicro.eu

SPF policy

  • include: _u.phcc.gov.qa._spf.smart.ondmarc.com

Threat-feed evidence

History

Related pages

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