Skip to content

Hostname

shift4payments.com

Last fetched

shift4payments.com resolves to 100.26.19.84, announced in 100.42.32.0/20 by AMAZON-AES - Amazon.com, Inc. in US. shift4payments.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 · shift4payments.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/shift4payments.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
2a5f9644-5311-4f17-bbdb-da44cd1ed847@identity-protect.org, 2d847855-efa1-4fa6-9728-8d2b690e5287@identity-protect.org, 6a12a6e9-8c90-4f80-adbc-23da22fe90f9@identity-protect.org, 8372a714-7d10-4e14-a641-9fd8bb960e0e@identity-protect.org, df3f38ab-643e-45ff-9d3e-5e924a0146d4@identity-protect.org, e63d9fef-f981-4d05-a146-cbb3fe502160@identity-protect.org, owner-11142651@shift4payments.com.whoisprivacyservice.org, owner-3432373@shift4payments.com.whoisprivacyservice.org, owner-6912554@shift4payments.com.whoisprivacyservice.org, owner-7039256@shift4payments.com.whoisprivacyservice.org

Subdomains

Mail and authentication

Nameservers

  • ns-103.awsdns-12.com
  • cass.ns.cloudflare.com
  • ns-812.awsdns-37.net
  • ns-1341.awsdns-39.org
  • ns-1669.awsdns-16.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
  • tempmail.shift4corp.com
  • shift4payments-com.mail.protection.outlook.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • ip: 207.99.28.68
  • ip: 216.164.166.33

Threat-feed evidence

History

Related pages

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