Does glencore.com have DMARC protection against email spoofing?

Yes. glencore.com publishes a DMARC record with p=reject at 100% coverage, so receiving providers should reject mail forged from @glencore.com.

How is glencore.com's C security grade calculated?

CyberTrust scores glencore.com passively across 6 area(s) — external attack surface 100/100; reputation and credential exposure 100/100; DNS hygiene 92/100; email spoofing defences (SPF/DKIM/DMARC) 84/100; TLS encryption and certificates 49/100; HTTP security headers 8/100 — and combines them by weight into the overall score of 75/100, which maps to grade C.

How many subdomains does glencore.com expose?

This scan observed 81 publicly resolvable subdomain(s) for glencore.com. Verified owners get the full list, with each host's open ports and running services.

Public security report

glencore.com security rating

75/100

A means lowest risk and F means highest, like a school report card. How the score is calculated →

Scanned 2026-10-30 · 10 issue(s) found · 16 checks passed

Re-scan glencore.com now

What this scan found

CyberTrust assessed glencore.com passively — using only information that is publicly visible on the internet: DNS records, certificates, response headers and reachable services. The result is 75/100, grade C, where A means lowest risk and F means highest, like a school report card.

Email spoofing is blocked: glencore.com publishes a DMARC record with p=reject at 100% coverage, so mail forged from @glencore.com should be rejected by major providers.

Strongest area: external attack surface (100/100). Weakest area: HTTP security headers (8/100).

10 issue(s) need attention (1 high, 1 medium, 8 low), while 16 checks passed.

Infrastructure observed: mail is hosted by proofpoint, DNS is served by google.

81 subdomain(s) of glencore.com resolve publicly.

Score by category

Area	Score	Grade	Issues
DNS hygiene	92	A	1
email spoofing defences (SPF/DKIM/DMARC)	84	B	2
external attack surface	100	A	0
IP threat intelligence	—	—	0
reputation and credential exposure	100	A	0
TLS encryption and certificates	49	F	2
HTTP security headers	8	F	5

Issues found (10)

highFront-end bundle leaks a Google Gemini / AI Studio key

A Google Gemini / AI Studio secret is compiled into a client-side JavaScript bundle. Anyone viewing the page source — including crawlers and attackers — can extract it and spend your quota or reach your private models.

1 asset(s) affected · worth +6 points · how to set HSTS, CSP and other security headers →

mediumCertificate chain is incomplete

Desktop browsers often fill the gap, but mobile apps, APIs and some browsers fail outright - so it works in your tests and breaks for real users.

4 asset(s) affected · worth +5 points · check a certificate with the free SSL tool →

lowNo OCSP stapling

The server does not staple the certificate revocation status. Every revocation check becomes an extra round trip to the CA, which slows the first visit and, if the CA endpoint is unreachable or the visitor's network blocks it, leaves the browser without a usable revocation status.

6 asset(s) affected · worth +2 points · check a certificate with the free SSL tool →

lowCookies without Secure/HttpOnly (samlPreauthSessionHash)

Missing Secure lets cookies travel in plaintext; missing HttpOnly lets injected scripts steal sessions; missing SameSite enables CSRF. Affected: samlPreauthSessionHash.

5 asset(s) affected · worth +2 points · how to set HSTS, CSP and other security headers →

lowContent Security Policy is weak (script-src 'unsafe-inline'; script-src 'unsafe-eval'; script-src wildcard/scheme source; object-src not restricted)

The policy is too permissive (script-src 'unsafe-inline'; script-src 'unsafe-eval'; script-src wildcard/scheme source; object-src not restricted), so injected scripts still run while giving a false sense of security.

5 asset(s) affected · worth +2 points · how to set HSTS, CSP and other security headers →

lowHSTS preload not enabled

Even with HSTS on, the very first visit is still exposed to SSL-stripping: the header only takes effect after one successful HTTPS visit. Browsers ship a preload list (Chromium's list is used by Chrome, Edge, Safari and Firefox) so the first connection goes straight to HTTPS.

2 asset(s) affected · worth +2 points · how to set HSTS, CSP and other security headers →

lowWeak DKIM key: 1024-bit RSA (selector k1)

At 1024 bits (selector k1) the key is considered weak; 1024-bit keys can be broken cheaply, letting attackers sign mail that passes DKIM.

1 asset(s) affected · worth +2 points · look up DKIM keys with the free DKIM tool →

lowNo MTA-STS policy

Without it an attacker on the network path can force a downgrade to plaintext and read or modify mail such as contracts and payment details.

1 asset(s) affected · worth +2 points · how to stop email spoofing with SPF, DKIM and DMARC →

lowNo Content Security Policy

Without it, any injected script runs: session theft, fake payment forms, or card-skimming scripts on compromised pages. CSP limits the damage even when something else fails.

2 asset(s) affected · worth +1 points · how to set HSTS, CSP and other security headers →

lowDNSSEC not enabled

Without it, attackers can poison caches or forge answers and send visitors to a lookalike server that harvests credentials.

1 asset(s) affected · worth +1 points · what DNSSEC prevents and how to enable it →

Checks passed

Mail exchangers configured
SPF record is valid
DMARC policy is enforced
Name servers are redundant
CAA restricts which CAs may issue certificates
HSTS enabled
Clickjacking protection enabled
MIME sniffing disabled
security.txt published
Content Security Policy in place
Only modern TLS versions are enabled
No weak cipher suites accepted
Certificate is valid and trusted
No risky services found exposed
No shadow-AI services exposed
No mail-server IP on spam blocklists

What we detected

mail provider: proofpoint
dns provider: google
subdomain count: 81

What could not be fully checked

No BIMI record
BIMI shows your logo next to authenticated mail in supporting inboxes (requires an enforcing DMARC policy). It is a trust signal rather than a security control, so it does not affect your score.
No TLS-RPT record
TLS-RPT sends you reports when other servers fail to deliver mail to you securely. Recommended alongside MTA-STS.
No Referrer-Policy 8 host(s)
Browsers default to strict-origin-when-cross-origin today; setting it explicitly is good hygiene.
No Permissions-Policy 8 host(s)
Permissions-Policy disables powerful browser features (camera, microphone, geolocation) you do not use.
No security.txt
security.txt (RFC 9116) tells security researchers how to report vulnerabilities to you instead of posting them publicly.
Website not reachable 2 host(s)
The site could not be fetched, so its response headers and page content were not checked.
HTTPS not available on port 443 2 host(s)
The TLS checks could not run on this host, so its TLS configuration was not verified.
TLS 1.3 not enabled 5 host(s)
TLS 1.3 is faster and removes legacy cryptography. Recommended, but not required.
RSA key exchange still accepted 4 host(s)
Static RSA key exchange is kept for old clients. It lacks forward secrecy but is not scored when ECDHE is available.

Frequently asked questions about glencore.com security

Does glencore.com have DMARC protection against email spoofing?: Yes. glencore.com publishes a DMARC record with p=reject at 100% coverage, so receiving providers should reject mail forged from @glencore.com.
How is glencore.com's C security grade calculated?: CyberTrust scores glencore.com passively across 6 area(s) — external attack surface 100/100; reputation and credential exposure 100/100; DNS hygiene 92/100; email spoofing defences (SPF/DKIM/DMARC) 84/100; TLS encryption and certificates 49/100; HTTP security headers 8/100 — and combines them by weight into the overall score of 75/100, which maps to grade C.
What is the most serious issue found on glencore.com?: Front-end bundle leaks a Google Gemini / AI Studio key (severity high). A Google Gemini / AI Studio secret is compiled into a client-side JavaScript bundle. Anyone viewing the page source — including crawlers and attackers — can extract it and spend your quota or reach your private models. Fixing it is worth about +6 points.
How many subdomains does glencore.com expose?: This scan observed 81 publicly resolvable subdomain(s) for glencore.com. Verified owners get the full list, with each host's open ports and running services.

What a verified owner of glencore.com sees

Everything above is what anyone can observe from the internet. Domain owners who verify ownership additionally get the full asset inventory — every subdomain with its open ports and running services — look-alike and typosquatting domains registered against the brand, credential-exposure monitoring, and copy-paste fixes for each finding.

Verify ownership of glencore.com (free) → Open the live interactive report →