Skip to content

Hostname

propiols.com

Last fetched

propiols.com resolves to 3.131.150.69, announced in 3.131.0.0/16 by AMAZON-02 - Amazon.com, Inc. in US. propiols.com 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 · propiols.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.9/10canon.whisper.security/host/propiols.com

Resolution chain

IPv6 resolution

No AAAA record for propiols.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1387
Registrant organisation
brian simkins
Contact emails
snikmisks@hotmail.com, d2caaad1af@propiols.com.whoistrustee.com, 5e629a881c6ed5edbf824510441b1c77fd1771d0e2c9572400269a38ca327d23@propiols.com.whoisproxy.org, 813830003381462072f06edbb40cf93e68636bab4d0234a832d50fc1f13cd73b@propiols.com.whoisproxy.org, 9bc485ea0690802ba65367983f833e4cdd8e118f925c0b5887fbfb5aaeb4f1dc@propiols.com.whoisproxy.org, b4667f28cc3dfba64fa486dd7f4463dbce97658fb7d9da9e46e7212a7a5a310f@propiols.com.whoisproxy.org, f303bc248aa0c657e388f8efeb0fc0cb8b39d5f56760200f1f312b1e1f258e00@propiols.com.whoisproxy.org

Subdomains

Subdomain
mail.propiols.com
wildcard.propiols.com
www.propiols.com

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • ns-122.awsdns-15.com
  • ns1.dnsimple.com
  • ns3.dnsimple.com
  • ns1.dnsimple-edge.com
  • ns3.dnsimple-edge.io
  • ns-757.awsdns-30.net
  • ns2.dnsimple-edge.net
  • ns-1104.awsdns-10.org
  • ns4.dnsimple-edge.org
  • ns-1938.awsdns-50.co.uk

MX records

  • d314069a.ess.barracudanetworks.com
  • d314069b.ess.barracudanetworks.com

SPF policy

  • include: _u.propiols.com._spf.dmarclf.com

Threat-feed evidence

History

Related pages

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