Skip to content

Hostname

petitionspot.com

Last fetched

petitionspot.com resolves to 13.227.192.125, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. petitionspot.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 · petitionspot.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/petitionspot.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of petitionspot.com owner
Contact emails
eb8f87d4b46141a7957214624554e6a6.protect@whoisguard.com, 8738d767f22e459bb366f389b42aaaa8.protect@withheldforprivacy.com, c5cdea9d-df0e-40bb-b040-7689615aa544@identity-protect.org, tech_ops@change.org

Subdomains

Subdomain
dc-8081345d.petitionspot.com
spam.petitionspot.com
widgets.petitionspot.com
wildcard.petitionspot.com
www.petitionspot.com

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-331.awsdns-41.com
  • ns-933.awsdns-52.net
  • 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
  • ns-1213.awsdns-23.org
  • ns-1924.awsdns-48.co.uk

Threat-feed evidence

History

Related pages

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