Does oocl.com have DMARC protection against email spoofing?

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

How is oocl.com's D security grade calculated?

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

How many subdomains does oocl.com expose?

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

Public security report

oocl.com security rating

63/100

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

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

Re-scan oocl.com now

What this scan found

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

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

Strongest area: external attack surface (100/100). Weakest area: TLS encryption and certificates (0/100).

15 issue(s) need attention (3 high, 4 medium, 8 low), while 10 checks passed.

Infrastructure observed: mail is hosted by microsoft.

121 subdomain(s) of oocl.com resolve publicly.

Score by category

Area	Score	Grade	Issues
DNS hygiene	84	B	2
email spoofing defences (SPF/DKIM/DMARC)	44	F	3
external attack surface	100	A	0
IP threat intelligence	—	—	0
reputation and credential exposure	100	A	0
TLS encryption and certificates	0	F	6
HTTP security headers	51	F	4

Issues found (15)

highSPF authorizes huge IP ranges (ip4:40.92.0.0/15, ip4:52.100.0.0/15)

Very large ranges (ip4:40.92.0.0/15, ip4:52.100.0.0/15) let anyone inside them - for example any customer of the same cloud provider - send mail as you.

1 asset(s) affected · worth +7 points · check an SPF record with the free SPF tool →

highCertificate does not match the hostname

This certificate is issued for localhost.localdomain, so browsers warn; typical causes are missing the bare domain, a stale name, or an incomplete SAN list.

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

highCertificate is not trusted (self-signed)

This certificate cannot be chained (self-signed), so visitors get a warning - and repeated warnings teach people to click through, which defeats warnings during real attacks.

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

mediumOutdated TLS versions enabled (TLSv1.0, TLSv1.1)

Versions TLSv1.0, TLSv1.1 are formally deprecated, fail PCI DSS requirements and are no longer supported by modern browsers; they also enable downgrade attacks and fail compliance audits.

2 asset(s) affected · worth +3 points · how to read an SSL/TLS certificate check →

mediumHSTS not enabled

Without it, an attacker can strip SSL on the first HTTP request and keep the user on plaintext (SSL stripping), a common attack on public Wi-Fi.

2 asset(s) affected · worth +3 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.

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

mediumCertificate expires in 9 days

Only 9 days remain, which usually means automated renewal already failed - unattended, that becomes a full outage at expiry.

1 asset(s) affected · worth +2 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.

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

lowNo CAA record

Without it any CA may issue certificates for your domain, enabling a lookalike site with a valid padlock.

1 asset(s) affected · worth +1 points · see who can issue certificates with the free CAA tool →

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 →

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

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

1 asset(s) affected · worth +1 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 +1 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.

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

lowServer reveals software versions

Exact versions let attackers look up ready-made exploits instead of probing - most intrusions start with a version scan.

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

lowX-Content-Type-Options missing

Without it a file uploaded as an image can be executed as HTML/JavaScript on your domain, stealing same-site cookies and sessions.

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

Checks passed

Mail exchangers configured
DMARC policy is enforced
Name servers are redundant
Clickjacking protection enabled
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: microsoft
subdomain count: 121

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.
Website returned an error page — partly unassessed 2 host(s)
The page returned HTTP 403 (often a firewall challenge for automated clients), so most header and content checks could not run. HSTS was still assessed where the response is reliable, but this category is only partially evaluated and its score should be read as incomplete.
Website not reachable 7 host(s)
The site could not be fetched, so its response headers and page content were not checked.
No Referrer-Policy
Browsers default to strict-origin-when-cross-origin today; setting it explicitly is good hygiene.
No Permissions-Policy
Permissions-Policy disables powerful browser features (camera, microphone, geolocation) you do not use.
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 2 host(s)
Static RSA key exchange is kept for old clients. It lacks forward secrecy but is not scored when ECDHE is available.
HTTPS not available on port 443 4 host(s)
The TLS checks could not run on this host, so its TLS configuration was not verified.

Frequently asked questions about oocl.com security

Does oocl.com have DMARC protection against email spoofing?: Yes. oocl.com publishes a DMARC record with p=reject at 100% coverage, so receiving providers should reject mail forged from @oocl.com.
How is oocl.com's D security grade calculated?: CyberTrust scores oocl.com passively across 6 area(s) — external attack surface 100/100; reputation and credential exposure 100/100; DNS hygiene 84/100; HTTP security headers 51/100; email spoofing defences (SPF/DKIM/DMARC) 44/100; TLS encryption and certificates 0/100 — and combines them by weight into the overall score of 63/100, which maps to grade D.
What is the most serious issue found on oocl.com?: SPF authorizes huge IP ranges (ip4:40.92.0.0/15, ip4:52.100.0.0/15) (severity high). Very large ranges (ip4:40.92.0.0/15, ip4:52.100.0.0/15) let anyone inside them - for example any customer of the same cloud provider - send mail as you. Fixing it is worth about +7 points.
How many subdomains does oocl.com expose?: This scan observed 121 publicly resolvable subdomain(s) for oocl.com. Verified owners get the full list, with each host's open ports and running services.

What a verified owner of oocl.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 oocl.com (free) → Open the live interactive report →