Skip to content

Hostname

pes.edu

Last fetched

pes.edu resolves to 20.193.137.15, announced in 20.192.0.0/10 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in IN. pes.edu 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 · pes.eduRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/pes.edu

Resolution chain

IPv6 resolution

No AAAA record for pes.edu is recorded in WhisperGraph.

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
peoples education society

Subdomains

Subdomain
aatmatrisha.pes.edu
aeolus.pes.edu
alumni.pes.edu
amaatra.pes.edu
arch.pes.edu
bbasm.pes.edu
bt.pes.edu
campaigns.pes.edu
careers.pes.edu
chips.pes.edu
cie.pes.edu
civil.pes.edu

Showing 12 of 137. 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.pesuniversity.com
  • ns2.pesuniversity.com
  • 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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.google.com
  • a: pes.edu
  • mx: pes.edu
  • include: eig.spf.a.cloudfilter.net
  • include: sendgrid.net
  • ip: 119.18.62.183
  • ip: 207.174.215.159

Threat-feed evidence

History

Related pages

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