Skip to content

Hostname

as.pitt.edu

Last fetched

as.pitt.edu resolves to 1 IPv4 address operated by UPITT-AS - University of Pittsburgh in US.

Nutrition Label

WHISPER CANON · as.pitt.eduRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/as.pitt.edu

Resolution chain

as.pitt.edu resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
136.142.34.30136.142.0.0/16AS4130UPITT-AS - University of PittsburghUS

WHOIS identity

No WHOIS records are currently associated with as.pitt.edu in WhisperGraph.

Subdomains

86 observed subdomains of as.pitt.edu.

Subdomain
ad-44lbd42.as.pitt.edu
alt-as-fs-01.as.pitt.edu
as-019-080.as.pitt.edu
as-1mf79h2.as.pitt.edu
as-2fz79h2.as.pitt.edu
as-3pf79h2.as.pitt.edu
as-41t79h2.as.pitt.edu
as-4dx3td2.as.pitt.edu
as-4fpcfx1.as.pitt.edu
as-5vrrgc2.as.pitt.edu
as-ar-g6bn91300.as.pitt.edu
as-awstmngr-00.as.pitt.edu
as-cnf79h2.as.pitt.edu
as-desc-dev.as.pitt.edu
as-descartes-qa.as.pitt.edu
as-dmf79h2.as.pitt.edu
as-do-101364693.as.pitt.edu
as-do-9j9xp13.as.pitt.edu
as-do-brqsn53.as.pitt.edu
as-do-cl-910-ricoh-mp2555.as.pitt.edu
as-do-cl-917-ricoh-mp2555.as.pitt.edu
as-do-cl-928-lexmark-c510.as.pitt.edu
as-do-cl-928-ricoh-mp2555.as.pitt.edu
as-do-d42qnf2.as.pitt.edu
as-fs-01.as.pitt.edu

Showing 25 of 86. View all subdomains →

Web-graph footprint

Distinct hostnames that link to or from as.pitt.edu in the public web crawl.

118 sites link to this hostname.

432 sites linked to from this hostname.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

4 SPF mechanisms authorising senders for as.pitt.edu.

MechanismTarget
SPF_INCLUDE_spf.qualtrics.com
SPF_INCLUDEspf.protection.outlook.com
SPF_IP136.142.11.128/27
SPF_IP136.142.251.0/25

Related pages

Pivot deeper into the graph from as.pitt.edu.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "as.pitt.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.