Skip to content

Hostname

pendulumlife.com

Last fetched

pendulumlife.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. pendulumlife.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 · pendulumlife.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/pendulumlife.com

Resolution chain

No IPv4 resolution is recorded for pendulumlife.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:468
Registrant organisation
chad rickard
Contact emails
chad.rickard@gmail.com, 196344ae-cb20-4e89-bec0-b8c5d9da1622@identity-protect.org, 5af0ee29-9a76-40d0-81bb-8e2b89a6ee0b@identity-protect.org, 698590bd-767a-4377-9d89-b3aecde67c3c@identity-protect.org, 7cc3e63c-a9ac-4e27-9248-6dc01befc56d@identity-protect.org, 83c5405d-2cfa-43cd-ac93-319dbb14e827@identity-protect.org, fed7fa63-9fc6-49b5-8aa5-9bcca6ed2669@identity-protect.org, owner-1702302@pendulumlife.com.whoisprivacyservice.org, owner-9930776@pendulumlife.com.whoisprivacyservice.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

  • ns-86.awsdns-10.com
  • ns-899.awsdns-48.net
  • ns-1154.awsdns-16.org
  • ns-1584.awsdns-06.co.uk

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
  • include: shops.shopify.com
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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