Dataweaz

qualcomm.com

Summary

Registrar
MarkMonitor Inc.
Status
clientDeleteProhibited
Created on
July 7, 1988
Expires on
July 6, 2027
Name servers
ns2.qualcomm-inc.com, ns1.qualcomm-inc.com
Mail servers
mxa-0031df01.gslb.pphosted.com, mxb-0031df01.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 qualcomm.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
[email protected]

Record

v=DMARC1; p=reject; sp=reject; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected];

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 qualcomm.com.

RuleValueResult
include%{ir}.%{v}.%{d}.spf.has.pphosted.comAllowed
all—Suspicious

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all

E-mail signing (DKIM)

DKIM keys published by qualcomm.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 1024 bits · shortActive
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 qualcomm.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from qualcomm.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 @qualcomm.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

qualcomm.com  MX  10 mx1.qualcomm.com.
qualcomm.com  MX  20 mx2.qualcomm.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.qualcomm.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

qualcomm.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.qualcomm.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.qualcomm.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.qualcomm.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.qualcomm.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 qualcomm.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.

TypeIP address
A129.46.98.181

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
ns2.qualcomm-inc.com162.159.6.245
ns1.qualcomm-inc.com162.159.2.242

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @qualcomm.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
0mxa-0031df01.gslb.pphosted.com205.220.180.131
0mxb-0031df01.gslb.pphosted.com205.220.180.131

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.qualcomm.com.

NameContent
qualcomm.comamazonses:LqjURlqhFIXwItRqOwyKmJaeLHrNBGgZjn7yzzXV9Sk=
qualcomm.comsmartsheet-site-validation=Q6puf_91JTZEGmR3aEKFm8JFbuwAXWbz
qualcomm.comstripe-verification=9fc6d6be21c4c6bff9e0536b1861419f2c3ee3539ea62b17b166f754d537ce29
qualcomm.comamazonses:Hmx0VxKU5jLCdDf+X9WRm/8keBRAQk/aUAacqqiWtog=
qualcomm.comstripe-verification=d434ae6606e342d3bd5829c1e68d237362b8a00bd089de1ff30d1edf09fc1a22
qualcomm.com5GwpWw73hjRr9eLCmy7ixwrgyGFY6wnOGtNZ1Lpa2wzByqAAsyx0bNUy7rtNDnyZzIrcHPFm0MYcC+kVbzcBSg==
qualcomm.comgoogle-site-verification=a9xhK4Hc6ek8GfpzdpYw6m__fWem19Z-pzAQx5iJMg8
qualcomm.comatlassian-domain-verification=fA3UGDxLoxNQ2hD3O/ZY7RdpXAVrGvtCG3F4FVBsp8YFuavpoI1ijtpDRGHPwogQ
qualcomm.combv-domain-verification=4d20ce3e557e5cb5c3753bc3a3354e927b5c6b594268b265280dc7a76ed8262e
qualcomm.com5b861f155b59df07bb46db2317ba1f95fee6b7548d2f67a4050098d77229aa81
qualcomm.comdocusign=8fa07369-5355-4bf2-b84c-30a3170421ae
qualcomm.comcitrix.mobile.ads.otp=y2p9t51mi866b61zgpqz7x
qualcomm.comatlassian-sending-domain-verification=d52a799e-780b-4fb4-9fee-7015fc176085
qualcomm.comadobe-idp-site-verification=df216429595aa1fdc46c1b866a8723fb509d2dedd2f00e52eb3b39c9b1ccbec1
qualcomm.comonetrust-domain-verification=743c6ff33b914d3ea61b6602f216ae1e
qualcomm.com]bv-domain-verification=4d20ce3e557e5cb5c3753bc3a3354e927b5c6b594268b265280dc7a76ed8262e
qualcomm.comLinear-domain-verification=psuwjnh9fyjk
qualcomm.comwiz-domain-verification=88da4e9f27d4b6cc7c8643b4237ad19b9bc2240bbf7d8193fbc0ce236e50d4de
qualcomm.comflexera-domain-verification-jcnuuhvxbbxbkrcp
qualcomm.comcursor-domain-verification-kx08sm=gvKxfw9GTeMeMt9e6OVa04UFI
qualcomm.comv=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
qualcomm.comairtable-verification=77d9b09e023b204f9315558888677428
qualcomm.comadobe-aem-verification=www.stgpreview.qualcomm.com/99552/1015123/5109dfcd-d152-4177-9843-67e90c143fac
qualcomm.com6s5hre94HNteMjhN7S+fDl2fEMz+Obh2F/I6rJ8G4G5DCvf+81ywXRtbZsrnXs1qZy7U2MDndOwgtvGa9cKrbg==
qualcomm.comdocker-verification=e01f77bb-044e-4e30-a47f-8ed3f5ad159c
qualcomm.comsophos-domain-verification=7e5f78cba2a21772d1ebff95e2937f3e9c90ef4c09f07061fd5ef0ba5f10c587
qualcomm.comMS=ms95225044
qualcomm.comdtm-domain-verification=gXZCIWTwPOESGGdOwzm_dKPPmxwaF0z2mQqDfVG7Atw
qualcomm.comwebexdomainverification.4C675B8BD209B136E053AB06FC0A3F65=5b1b5551-c9a0-47fe-8d9e-1f4be37dac93
qualcomm.comms-domain-verification=a4356a70-face-4e82-92a7-c97ac8b16f61
qualcomm.comgoogle-site-verification=tdo0FH0sdEMLC1RLWbBGTaFOwAGFjm2kwHuCO03-TDE
qualcomm.combettercomp-verify=aef765684d18f901959ee72bacfc6a03dae32a43ed45c086e558984c9a4e4a98
qualcomm.comwiz-domain-verification=692573d1c274f2713026d823116e1542fc3653d5aae8b4d62f4195c8d58ec7f0
qualcomm.compaloaltonetworks-site-verification=2ce3ab376f96cb46b0725c5650bbff886b431d993a247aaca4da75623abdf579
qualcomm.comdocusign=7a11592c-96ac-4463-9711-694ab67bad1f
qualcomm.comapple-domain-verification=CPjsdGqIeTWKHSU8
qualcomm.comMS=ms88176711
_dmarc.qualcomm.comv=DMARC1; p=reject; sp=reject; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected];
k2._domainkey.qualcomm.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.qualcomm.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
s1._domainkey.qualcomm.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC/afD4lSH1HL9xGvo+/kk5667a2hDH/Pj3vmuoZCBpaxRlcpSau7DKcXWu7oZT/enmo0S84tGzpvskATR/fmZ43bDMJMxB4rSbDDco8K5kCnsoflggRlRfiFt30XurloOhM3IKwGrNkiWxd5E3tHbQlfTDM98q2ZbvOfx6quEJlwIDAQAB
s2._domainkey.qualcomm.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC08Xb5npjl2Q//Uet5BqBMGug0MwJgeCIH5vbieFaC/t9wAwC1wZBAG84qubh7cQWF63cL8CYLN7dgAzSEoqAQJl4cW+TbvlV3F7teN+bui5KLpqJop2VyiBvgI2Zi40v1fMHAgpZ8z/zXasbr9Ucy5Dd9NlDnKGF8p/Ryqe6PSQIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
129.46.98.181Website129.46.98.0/24
162.159.6.245Name server ns2.qualcomm-inc.com162.159.6.0/24
162.159.2.242Name server ns1.qualcomm-inc.com162.159.2.0/24
205.220.180.131Mail server mxa-0031df01.gslb.pphosted.com, Mail server mxb-0031df01.gslb.pphosted.com205.220.180.0/24

WHOIS of the domain qualcomm.com

Domain Name: QUALCOMM.COM
   Registry Domain ID: 2281426_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.markmonitor.com
   Registrar URL: http://www.markmonitor.com
   Updated Date: 2025-06-04T12:10:15Z
   Creation Date: 1988-07-07T04:00:00Z
   Registry Expiry Date: 2027-07-06T04:00:00Z
   Registrar: MarkMonitor Inc.
   Registrar IANA ID: 292
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.2086851750
   Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
   Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
   Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
   Name Server: NS1.QUALCOMM-INC.COM
   Name Server: NS2.QUALCOMM-INC.COM
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T23:36: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.