Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
urbantakeover.at scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Security Headers. Positive signals: TLS Configuration, Known Breaches, HSTS Header 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 urbantakeover.at compares
Grade distribution across 2378 companies we've scanned. urbantakeover.at scores better than 64% 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
urbantakeover.at — Grade B- (80/100)
2378 companies scanned
Security checks
Each check inspects a different part of urbantakeover.at's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 1/5 security headers present. Missing: X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
DNS Configuration
Strengths: 2 nameservers configured (ns46.domaincontrol.com., ns45.domaincontrol.com.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest). Issues: No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=63072000 with includeSubDomains and preload. Meets best-practice configuration.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
CVE Exposure
Detected technologies: DPS/2.0.0, Starfield Technologies; Go Daddy Website Builder/8.0.0000. No high or critical CVEs found for detected versions.
Certificate Hygiene
Strengths: Certificate valid, 60 days remaining; Issued by GoDaddy.com, Inc..
Recommended actions
3 items
Steps to improve urbantakeover.at's security grade, ranked by impact.
1
Add missing security headers (X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
4 of 5 recommended security headers are missing on urbantakeover.at: 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: X-Content-Type-Options: nosniff
2
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
3
Add: Referrer-Policy: strict-origin-when-cross-origin
4
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
5
Verify with: curl -sI https://urbantakeover.at | 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
Strengthen email authentication configuration
Email authentication is partially configured for urbantakeover.at but has gaps. Actions needed: add SPF record; configure DKIM. 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
Add SPF record if missing: v=spf1 include:_spf.google.com -all
2
Configure DKIM and publish public key in DNS
3
Verify with: nslookup -type=txt _dmarc.urbantakeover.at
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for urbantakeover.at 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 .at TLD
4
Verify: dig +dnssec urbantakeover.at
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest). Issues: No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Missing
No SPF record found.
Security Headers
1/5 present
Missing: X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=63072000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 60 days remaining; Issued by GoDaddy.com, Inc..
DNSSEC
Not enabled
Strengths: 2 nameservers configured (ns46.domaincontrol.com., ns45.domaincontrol.com.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.