Skip to content

Hostname

pheaa.org

Last fetched

pheaa.org resolves to 12.177.52.116, announced in 12.177.52.0/24 by INS-AS - AT&T Enterprises, LLC in US. pheaa.org 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 · pheaa.orgRouting diversity1.5/10Peering density5.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/pheaa.org

Resolution chain

IPv6 resolution

No AAAA record for pheaa.org is recorded in WhisperGraph.

Attribution

at enterprises

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Contact emails
eu29w8vt2tr@networksolutionsprivateregistration.com, jz4wm4896sn@networksolutionsprivateregistration.com, k84n285c36x@networksolutionsprivateregistration.com, n688f2zg835@networksolutionsprivateregistration.com, z638n7uv94c@networksolutionsprivateregistration.com, z66sc6646hr@networksolutionsprivateregistration.com, z77qg49s55r@networksolutionsprivateregistration.com, aesjla@aessuccess.org, wmiller@pheaa.org

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • dbru.br.ns.els-gms.att.net
  • dmtu.mt.ns.els-gms.att.net
  • ns2.aessuccess.org
  • ns1.pheaa.org

MX records

  • pheaa-org.mail.protection.outlook.com

SPF policy

  • ip: 12.177.52.0/24
  • ip: 199.59.200.201/32
  • include: amazonses.com
  • include: spf.protection.outlook.com
  • a: pheaa.org
  • mx: pheaa.org
  • ip: 34.195.26.64
  • ip: 34.198.6.229
  • ip: 34.199.21.82
  • ip: 34.199.75.122
  • ip: 52.45.211.65
  • ip: 54.240.121.127
  • ip: 54.240.121.128

Threat-feed evidence

History

Related pages

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