Skip to content

Hostname

openpowerlifting.org

Last fetched

openpowerlifting.org resolves to 45.55.106.19, announced in 45.55.104.0/22 by DIGITALOCEAN-ASN - DigitalOcean, LLC in US. openpowerlifting.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 · openpowerlifting.orgRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/openpowerlifting.org

Resolution chain

IPv6 resolution

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

Attribution

digitalocean

ORIGIN_AS

WHOIS identity

Registrar
iana:895
Registrant organisation
contact privacy inc. customer 12481573
Contact emails
jivbhobjxsqs@contactprivacy.email, owner@openpowerlifting.org.whoisproxy.org

Subdomains

Subdomain
beta.openpowerlifting.org
book.openpowerlifting.org
docs.openpowerlifting.org
ru.openpowerlifting.org
www.openpowerlifting.org

Showing 5 of 5 subdomains (5 per page).

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

  • ns-cloud-a1.googledomains.com
  • ns-cloud-a2.googledomains.com
  • ns-cloud-a3.googledomains.com
  • ns-cloud-a4.googledomains.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

  • mxa.mailgun.org
  • mxb.mailgun.org

SPF policy

  • include: mailgun.org

Threat-feed evidence

History

Related pages

Pivot from openpowerlifting.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: "openpowerlifting.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.