Hostname
pwcs.edu
Last fetched
pwcs.edu is a registered hostname under the .edu top-level domain. Live infrastructure data is temporarily unavailable; refresh in a moment.
Nutrition Label
Resolution chain
Resolution chain data is temporarily unavailable. Refresh in a moment to retry.
WHOIS identity
- Registrar
- —
- Organization
- prince william county schools
- Contact emails
- —
Subdomains
179 observed subdomains of pwcs.edu.
Showing 25 of 179. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from pwcs.edu in the public web crawl.
595 sites link to this hostname.
481 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
37 SPF mechanisms authorising senders for pwcs.edu.
| Mechanism | Target |
|---|---|
| SPF_EXISTS | mx1.hc2916-71.iphmx.com |
| SPF_EXISTS | mx2.hc2916-71.iphmx.com |
| SPF_INCLUDE | app.sgizmo.com |
| SPF_INCLUDE | mail.zendesk.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 146.20.113.0/24 |
| SPF_IP | 156.70.13.0/24 |
| SPF_IP | 174.140.129.48/28 |
| SPF_IP | 198.207.147.224/27 |
| SPF_IP | 199.223.255.0/27 |
| SPF_IP | 20.12.60.77 |
| SPF_IP | 2001:4838:101:2:66:117:61:24/64 |
| SPF_IP | 204.239.0.224/27 |
| SPF_IP | 208.42.137.0/24 |
| SPF_IP | 208.42.179.121/32 |
| SPF_IP | 208.42.179.123/32 |
| SPF_IP | 208.42.190.0/24 |
| SPF_IP | 209.134.144.240/28 |
| SPF_IP | 209.134.144.4/32 |
| SPF_IP | 209.134.151.0/24 |
| SPF_IP | 209.134.158.0/24 |
| SPF_IP | 216.128.251.155/32 |
| SPF_IP | 216.230.14.224/27 |
| SPF_IP | 216.71.137.128 |
| SPF_IP | 216.71.137.132 |
| SPF_IP | 216.71.137.133 |
| SPF_IP | 216.71.140.244 |
| SPF_IP | 216.71.140.251 |
| SPF_IP | 216.71.140.252 |
| SPF_IP | 66.117.61.24/32 |
| SPF_IP | 66.117.61.27/32 |
| SPF_IP | 69.5.85.128/25 |
| SPF_IP | 69.5.86.0/24 |
| SPF_IP | 69.5.87.0/24 |
| SPF_IP | 69.72.47.78/32 |
| SPF_IP | 69.90.103.215/32 |
| SPF_MX | pwcs.edu |
Related pages
Pivot deeper into the graph from pwcs.edu.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "pwcs.edu"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.