Skip to content

Hostname

ministryplatform.com

Last fetched

ministryplatform.com resolves to 13.248.160.137, announced in 13.249.0.0/24 by AMAZON-02 - Amazon.com, Inc. in CA. ministryplatform.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 · ministryplatform.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/ministryplatform.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
ministryplatform.com@domainsbyproxy.com, support@thinkministry.com, 79b6b4b9-c8f9-4b2c-8b5e-7d5c29f225e3@identity-protect.org, bc0c6163-97f9-4472-b9d0-2eab36711b36@identity-protect.org, cd2db36b-63cc-4d57-9331-4335bc0650d4@identity-protect.org, ce1b2d75-06a9-4591-9c2e-f86749ad7e76@identity-protect.org, db4afae0-58da-46a2-b997-c2d4d328adae@identity-protect.org, e7aedbf1-1543-4889-b8d8-c0ba079ac818@identity-protect.org, owner-10002769@ministryplatform.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-134.awsdns-16.com
  • ns-775.awsdns-32.net
  • ns-1077.awsdns-06.org
  • ns-1941.awsdns-50.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • a: ministryplatform.com
  • mx: ministryplatform.com
  • include: spf.protection.outlook.com
  • include: sendgrid.net
  • ip: 167.89.80.66

Threat-feed evidence

History

Related pages

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