Skip to content

Hostname

amvescap.com

Last fetched

amvescap.com resolves to 142.148.229.30, announced in 142.148.229.0/24 by INVESCO - Invesco Group Services, Inc. in US. amvescap.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 · amvescap.comRouting diversity1.5/10Peering density6.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/amvescap.com

Resolution chain

IPv6 resolution

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

Attribution

invesco group

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of amvescap.com owner
Contact emails
ncgwebservices@aimfunds.com, webservices@invesco.com, 6e9faaad-c92f-4f7e-b92e-777f9ef626da@identity-protect.org, 97137311-8b0b-4f88-bb7b-ca63fd9d0ce3@identity-protect.org, b2017e16-4d90-4e2d-94f0-4f8d71ccb535@identity-protect.org, ea7b59cb-51d8-44d9-9aad-4db9943af02a@identity-protect.org, ee1e96c0-9719-450a-b99a-1097373937cf@identity-protect.org, f3b9f692-734b-442a-8e5d-d41fce26a6ac@identity-protect.org

Subdomains

Subdomain
mail1.amvescap.com
mail2.amvescap.com
na.amvescap.com
ns3.amvescap.com
ns4.amvescap.com
ns5.amvescap.com

Showing 6 of 8. View all subdomains →

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-252.awsdns-31.com
  • ns-895.awsdns-47.net
  • aws-shared-dns.ops.invesco.net
  • ns-1363.awsdns-42.org
  • ns-1957.awsdns-52.co.uk

MX records

  • mxa-00192c01.gslb.pphosted.com
  • mxb-00192c01.gslb.pphosted.com

SPF policy

  • include: %{i}._ip.%{h}._ehlo.%{d}._spf.vali.email

Threat-feed evidence

History

Related pages

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