Dataweaz

invesco.com

Summary

Registrar
Amazon Registrar, Inc.
Status
clientTransferProhibited
Created on
January 4, 1995
Expires on
January 3, 2027
Name servers
ns-1566.awsdns-03.co.uk, ns-45.awsdns-05.com, ns-740.awsdns-28.net, ns-1336.awsdns-39.org
Mail servers
mxa-00192c01.gslb.pphosted.com, mxb-00192c01.gslb.pphosted.com
DMARC
Reject
SPF
Soft

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

DMARC tells mail servers what to do with an e-mail that claims to come from invesco.com but fails SPF and DKIM checks.

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
—

Record

v=DMARC1; p=reject; pct=100; adkim=r; aspf=r; rua=mailto:[email protected]; fo=1

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for invesco.com.

RuleValueResult
include%{i}._ip.%{h}._ehlo.%{d}._spf.vali.emailAllowed
all—Suspicious

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all

E-mail signing (DKIM)

DKIM keys published by invesco.com under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
k2MailchimpRSA 2048 bitsActive
k3MailchimpRSA 2048 bitsActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 1024 bits · shortActive

RSA keys shorter than 2048 bits, called short keys, are discouraged: they are easier to break.

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to invesco.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from invesco.com was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @invesco.com address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

invesco.com  MX  10 mx1.invesco.com.
invesco.com  MX  20 mx2.invesco.com.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.invesco.com.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

invesco.com  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.invesco.com, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.invesco.com  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.invesco.com, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.invesco.com  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of invesco.com

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
ns-1566.awsdns-03.co.uk205.251.198.30
ns-45.awsdns-05.com205.251.192.45
ns-740.awsdns-28.net205.251.194.228
ns-1336.awsdns-39.org205.251.197.56

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @invesco.com addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
5mxa-00192c01.gslb.pphosted.com148.163.149.205
5mxb-00192c01.gslb.pphosted.com148.163.149.205

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.invesco.com.

NameContent
invesco.comfastly-domain-delegation-hgjhh67ifxddsesr-14052020
invesco.comfastly-domain-delegation-mkfifhhh7-196823-2019-12-16
invesco.comfastly-domain-delegation-ydgvxl3-206786-2020-01-01
invesco.comgoogle-site-verification=B6aDoh4fKTGPUmP95xqijr2iuqXHnVmVJI66pxU3-hE
invesco.comgoogle-site-verification=OS0RXKKjTuRw8_v_dBw28kK3ZNNlXaH2xteZCuv1OB8
invesco.comgoogle-site-verification=RlSD97ZtIk2UxiGw4UzILgi6pk3Wv6gOQI48FGjaBww
invesco.comgoogle-site-verification=hsq3TSSFAvQJ2JWqcQ0yj0ZrJjCSMAhKqiC-lz5ndq8
invesco.cominfoblox-domain-mastery=89610b9b7dbab27da78074c25659690631ce2a161a08d988e2e94bf5385c204e9e
invesco.comjamf-site-verification=osSek21Kmq2lajOrxz0ztA
invesco.commf0t0kcgvd7w8413xhxh0ftmp7b9yb5l
invesco.commiro-verification=161de9815222b3d8d331ed397e4a0e549440c22e
invesco.comoTdo4ejT6+B2GJceCdgcThARVlcf9MfSmV8EKNXIIEKzWVusz7nqpQKOtMPkNVFitxGFmbKsJ5umNOewWLsWcQ==
invesco.comonetrust-domain-verification=65039e38e15a4880b34aadc522807812
invesco.comonetrust-domain-verification=93590e165fdd4c3e849f3dd6f2d527a8
invesco.compardot481331=ecc4a7c1eb7b8e74a76d3fb409800213a4ba0d67eeb0023fd98bbafd26d0315a
invesco.compardot804743=7672af2a8ae95b771562d3fe67406b2d12fa237993cecf57d6c92fba030ead7c
invesco.compoppulo-domain-verification=00a89dc4-b8fa-4027-ab19-536148e2a17b
invesco.comremarkable-domain-verification=4d557bb5-c6ab-4c61-8e58-1218de9089a1
invesco.comsending_domain804743=ea288518335abc6366fc7fc3714acc39f39e78d32d1b8d7b4cd2e573691e7178
invesco.comsnowflake-verification=be55348a-01a0-1000-834c-0000000003f7
invesco.comv=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
invesco.comwdNdcmW9iuAToMYvYlhF5WsF7amLI/8+9wRB56SSr3jktDVpuPWAwTRLxx2umlenpSuQyApiJqkg4MOITj/fAA==
invesco.com0ed1fe018a0887dbd012f4417abd1ed0fc6ac3bc15
invesco.comB0D0-3BFC-957F-4120-9174-EB1F-B04B-4747
invesco.comMS=ms73814536
invesco.comYt32kZEe3w8lG57oMDhw
invesco.comZOOM_verify_LOK_-FPSTTSNEcfEQpFH5w?
invesco.com_582toizn09dciyw4ub0ivf3z0fbfuom
invesco.com_eix3bo5geoon4rhronn7gu0xisktm9m
invesco.com_h17c819j8z80qs7i8ohe2gyiunoqwjd
invesco.comaccess-domain-verification=d71737fb529ce5c7553c72fd3d3b643ef0e007acd95acc31a7169ad498ad88a9
invesco.comadobe-idp-site-verification=49fc5095970baaf3a829b9a020d9cbbac487855833149cd45dfa086e4bcff797
invesco.comapple-domain-verification=qiFe74GDj9lcq5QQ
invesco.comatlassian-domain-verification=9UDAdvBO5oH5pzX2C3zoDWK5LBQzGrN5INpfygwHh2SYVsyi96Y5zNglqetSa5TR
invesco.combox-domain-verification=0df9aa37eeb547e75d8827e90542fbb59606d26dbaa7037f998e4a92c90f0f53
invesco.comciscocidomainverification=1c50acf6def3d63a04024503f3b2133d936b815c4ff59e240990fb1559aae8c7
invesco.comdocusign=06d87594-cb01-4433-a4f5-fc801aa7e954
invesco.comdocusign=edb27d3a-dfe3-4007-bc36-6b281975146d
invesco.comfastly-domain-delegation-FhTy65JBH>-311997-20201112
_dmarc.invesco.comv=DMARC1; p=reject; pct=100; adkim=r; aspf=r; rua=mailto:[email protected]; fo=1
k2._domainkey.invesco.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.invesco.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
s1._domainkey.invesco.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAprT9bb98ZJ/APWrA+DAKb76P1oeD+Jqpzz0C1PQCBfqeWei1reYGjhG4VPcDhXaB4CbT+4irOlQ/qBGpNZ5Bvlpwcx180rLT7Ars6YpvXtozIg1YzVNncCLisgqgVgsprOLklu9zATq64HfpW4pGHkygYpQKMkUcs47JbT1cd62CIhIXlYvgXHnzPBdWgGzoM9ZwrctxTjnxmif16qR3r6UVfxJSQ7HYLvyobs2xittO6vl8bjJjaNzAHk5T/XXsVgQd2HrV6fRLOVZ773TtLW0Leb2h8NDRUSnLnsoX5hFG5nRboQKYModXJmchlAHSYziqr6NMuYYpMR7BUopXCQIDAQAB
s2._domainkey.invesco.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDrrwH01Jdd8xP2c4GpVGEc3PpTjv+AfVSMC6scLcuA1L1dV54pQ7TiUF8uSCE3IUC1A6/0+0ehVHG2LzKkvcYfr+vHtc4bZLUjWhOZgJlAoEMhQsGeupp22+Pm54qrze+yOmM1LuBEwXn5ds5v7Wmy2dHp7bON9Ujri8Qk5/TJfwIDAQAB

Related IP addresses

IPv4 addresses used by invesco.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
151.101.66.203Website151.101.66.0/24
151.101.2.203Website151.101.2.0/24
151.101.130.203Website151.101.130.0/24
151.101.194.203Website151.101.194.0/24
205.251.198.30Name server ns-1566.awsdns-03.co.uk205.251.198.0/24
205.251.192.45Name server ns-45.awsdns-05.com205.251.192.0/24
205.251.194.228Name server ns-740.awsdns-28.net205.251.194.0/24
205.251.197.56Name server ns-1336.awsdns-39.org205.251.197.0/24
148.163.149.205Mail server mxa-00192c01.gslb.pphosted.com, Mail server mxb-00192c01.gslb.pphosted.com148.163.149.0/24

WHOIS of the domain invesco.com

Domain Name: INVESCO.COM
   Registry Domain ID: 3640328_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.registrar.amazon
   Registrar URL: http://registrar.amazon.com
   Updated Date: 2026-05-14T18:49:17Z
   Creation Date: 1995-01-04T05:00:00Z
   Registry Expiry Date: 2027-01-03T05:00:00Z
   Registrar: Amazon Registrar, Inc.
   Registrar IANA ID: 468
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.2024422253
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Name Server: NS-1336.AWSDNS-39.ORG
   Name Server: NS-1566.AWSDNS-03.CO.UK
   Name Server: NS-45.AWSDNS-05.COM
   Name Server: NS-740.AWSDNS-28.NET
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T16:21:28Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.