Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
network.ae scored 78/100, meeting baseline requirements but with 6 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers. Positive signals: MX Records & Mail Provider, HSTS Header, Cookie Security all passed.
3 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How network.ae compares
Grade distribution across 2522 companies we've scanned. network.ae scores better than 59% of them.
79
A+
25
A
183
A-
191
B+
72
B
353
B-
121
C+
116
C
324
C-
117
D+
94
D
241
D-
606
F
network.ae — Grade C+ (78/100)
2522 companies scanned
Security checks
Each check inspects a different part of network.ae's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
None of the 5 recommended security headers are present (missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy). This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
TLS Protocol Support
Strengths: TLS 1.2 supported; TLS 1.2 supported (consider enabling TLS 1.3). Protocol support: TLS 1.3: No, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DNS Configuration
Strengths: 6 nameservers configured (a3-65.akam.net., a13-66.akam.net., a1-193.akam.net., a26-64.akam.net.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
MX Records & Mail Provider
Strengths: Mail handled by Proofpoint; 2 MX record(s) configured; Multiple MX records provide redundancy; Equal-priority MX records (10) — standard round-robin load balancing for Proofpoint.
HSTS Header
HSTS enabled: max-age=15768000s (182 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: s1, s2).
CVE Exposure
Detected technologies: AkamaiGHost. (AkamaiGHost detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Certificate Hygiene
Strengths: Certificate valid, 91 days remaining; Issued by DigiCert Inc.
Recommended actions
3 items
Steps to improve network.ae's security grade, ranked by impact.
1
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
5 of 5 recommended security headers are missing on network.ae: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add a Content-Security-Policy header. Safe starting value (works with Google Fonts and inline styles/scripts): default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; script-src 'self' 'unsafe-inline'; upgrade-insecure-requests. Test your site after adding it, then tighten over time by removing 'unsafe-inline'.
2
Add: X-Content-Type-Options: nosniff
3
Add: X-Frame-Options: SAMEORIGIN (use DENY only if you never embed your pages in iframes)
4
Add: Referrer-Policy: strict-origin-when-cross-origin
5
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
6
Verify with: curl -sI https://network.ae | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for network.ae can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .ae TLD
4
Verify: dig +dnssec network.ae
3
Upgrade to TLS 1.3
network.ae negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect network.ae:443 -tls1_3
At a glance
Key data points from the scan.
TLS Version
TLSv1.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: s1, s2).
SPF Record
Present
v=spf1 include:spf.protection.outlook.com include:_spf.salesforce.com include:spf-004da001.pphosted.
Security Headers
0/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=15768000s (182 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 91 days remaining; Issued by DigiCert Inc.
DNSSEC
Not enabled
Strengths: 6 nameservers configured (a3-65.akam.net., a13-66.akam.net., a1-193.akam.net., a26-64.akam.net.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.