Skip to content

Hostname

qm.edu.sa

Last fetched

qm.edu.sa resolves to 34.166.112.156, announced in 34.166.64.0/18 by GOOGLE-CLOUD-PLATFORM - Google LLC in SA. qm.edu.sa 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 · qm.edu.saRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/qm.edu.sa

Resolution chain

IPv6 resolution

No AAAA record for qm.edu.sa is recorded in WhisperGraph.

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for qm.edu.sa. 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
email.qm.edu.sa
hcm.qm.edu.sa
help.qm.edu.sa
imutoon.qm.edu.sa
iquran.qm.edu.sa
j5.qm.edu.sa
listen.qm.edu.sa
me.qm.edu.sa
reg.qm.edu.sa
seg.qm.edu.sa
sharh.qm.edu.sa
www.qm.edu.sa

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

Sample outbound links

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
  • ns1.alis.sa
  • ns2.alis.sa

MX records

  • email.qm.edu.sa

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • a: qm.edu.sa
  • mx: qm.edu.sa

Threat-feed evidence

History

Related pages

Pivot from qm.edu.sa 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: "qm.edu.sa"})-[: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.