Skip to content

Hostname

providian.com

Last fetched

providian.com resolves to 146.143.134.138, announced in 146.143.128.0/18 by JPMORGAN-AS3486 - JPMorgan Chase & Co. in US. providian.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 · providian.comRouting diversity1.5/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/providian.com

Resolution chain

IPv6 resolution

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

Attribution

jpmorgan chase

ORIGIN_AS

WHOIS identity

Registrar
iana:292
Registrant organisation
domain administrator
Contact emails
domainregistration@jpmchase.com

Subdomains

Subdomain
www.providian.com

Showing 1 of 1 subdomain (1 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

Mail and authentication

Nameservers

  • ns0037.secondary.cloudflare.com
  • ns0246.secondary.cloudflare.com
  • ns05.jpmorganchase.com
  • ns06.jpmorganchase.com
  • ns1.jpmorganchase.com
  • ns2.jpmorganchase.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

  • cluster14.us.messagelabs.com
  • cluster14a.us.messagelabs.com

SPF policy

  • ip: 159.53.110.0/24
  • ip: 207.162.225.0/24
  • ip: 207.162.228.0/24
  • ip: 207.162.229.0/24
  • ip: 159.53.36.0/24
  • ip: 159.53.46.0/24
  • ip: 170.148.48.0/24
  • ip: 159.53.78.0/24
  • a: spf.jpmchase.com
  • ip: 196.37.232.50

Threat-feed evidence

History

Related pages

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