Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
accept.inc scored 62/100, meeting baseline requirements but with 1 finding that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: DMARC / Email Security. Positive signals: Known Breaches, TLS Configuration, CVE Exposure all passed.
2 action items identified, including 1 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How accept.inc compares
Grade distribution across 2378 companies we've scanned. accept.inc scores better than 26% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
accept.inc — Grade D- (62/100)
2378 companies scanned
Security checks
Each check inspects a different part of accept.inc's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: SPF record present with hard-fail (-all). Issues: No DMARC record found — email spoofing is not prevented; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
DNS Configuration
Strengths: 2 nameservers configured (dns102.registrar-servers.com., dns101.registrar-servers.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
HSTS Header
Could not fetch https://accept.inc — connection failed or timed out.
Security Headers
Could not fetch https://accept.inc — connection failed or timed out.
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
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.
Certificate Hygiene
Strengths: Certificate valid, 51 days remaining; Issued by Let's Encrypt.
Recommended actions
2 items
Steps to improve accept.inc's security grade, ranked by impact.
1
Set up email authentication (DMARC, DKIM)
Without email authentication, anyone can send emails that appear to come from accept.inc. This is the most common vector for phishing attacks targeting employees and customers. DMARC, DKIM are not configured.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
How to fix this
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
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 accept.inc 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 .inc TLD
4
Verify: dig +dnssec accept.inc
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
Not configured
Strengths: SPF record present with hard-fail (-all). Issues: No DMARC record found — email spoofing is not prevented; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 -all
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://accept.inc — connection failed or timed out.
SSL Certificate
Valid
Strengths: Certificate valid, 51 days remaining; Issued by Let's Encrypt.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (dns102.registrar-servers.com., dns101.registrar-servers.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.