Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
connectu.com scored 45/100 and does not currently meet the minimum security posture threshold. Multiple configuration gaps were identified that require attention before approval.
Positive signals: MX Records & Mail Provider, Known Breaches, CVE Exposure 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 connectu.com compares
Grade distribution across 2598 companies we've scanned. connectu.com scores better than 11% of them.
83
A+
25
A
190
A-
196
B+
75
B
362
B-
129
C+
114
C
330
C-
119
D+
95
D
252
D-
628
F
connectu.com — Grade F (45/100)
2598 companies scanned
Security checks
Each check inspects a different part of connectu.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
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.
DMARC / Email Security
Strengths: SPF record present with hard-fail (-all); DKIM configured (selectors: google). Issues: No DMARC record found — email spoofing is not prevented.
DNS Configuration
Strengths: 4 nameservers configured (ns-1964.awsdns-53.co.uk., ns-351.awsdns-43.com., ns-881.awsdns-46.net., ns-1285.awsdns-32.org.); 5 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.
Certificate Hygiene
Issues: Could not retrieve certificate details.
TLS Protocol Support
Could not connect to connectu.com:443 on any TLS version.
TLS Configuration
Could not complete TLS handshake with connectu.com:443 — [Errno -5] No address associated with hostname
HSTS Header
Could not fetch https://connectu.com — connection failed or timed out.
Security Headers
Could not fetch https://connectu.com — connection failed or timed out.
Cookie Security
Could not fetch connectu.com to analyze cookies: HTTPSConnectionPool(host='connectu.com', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("HTTPSConnection(host='connectu.com', port=443): Failed to resolve 'connectu.com' ([Errno -5] No address associated with hostname)"))
MX Records & Mail Provider
Strengths: Mail handled by Google Workspace; 5 MX record(s) configured; Multiple MX records provide redundancy.
Known Breaches
No known breaches found in public disclosure databases.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Recommended actions
3 items
Steps to improve connectu.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for connectu.com but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.connectu.com
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 connectu.com 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 .com TLD
4
Verify: dig +dnssec connectu.com
3
Review certificate configuration
Certificate issues found for connectu.com: . These are operational hygiene items, not immediate security risks.
How to fix this
1
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
Issues detected
Could not complete TLS handshake with connectu.com:443 — [Errno -5] No address associated with hostname
DMARC Policy
Not configured
Strengths: SPF record present with hard-fail (-all); DKIM configured (selectors: google). Issues: No DMARC record found — email spoofing is not prevented.
SPF Record
Present
v=spf1 include:_spf.google.com -all
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://connectu.com — connection failed or timed out.
SSL Certificate
Issues
Issues: Could not retrieve certificate details.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-1964.awsdns-53.co.uk., ns-351.awsdns-43.com., ns-881.awsdns-46.net., ns-1285.awsdns-32.org.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.