Is umfrage.magenta.at safe to use as a vendor?

umfrage.magenta.at scored 80/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 9 checks passed, 5 warnings, 1 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does umfrage.magenta.at use?

umfrage.magenta.at uses TLSv1.3 with TLS_AES_128_GCM_SHA256. TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does umfrage.magenta.at have SPF configured?

Yes. SPF record found: v=spf1 mx a:mailext.magenta.at include:_spft.telekom.com include:rnmk.com includ...

Does umfrage.magenta.at have security headers configured?

umfrage.magenta.at has 2 of 5 recommended security headers. Present: CSP, X-Content-Type-Options. Missing: X-Frame-Options, Referrer-Policy, Permissions-Policy.

Does umfrage.magenta.at use HSTS?

Yes. HSTS enabled: max-age=31556926s (365 days) with includeSubDomains and preload. Meets best-practice configuration.

Has umfrage.magenta.at been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does umfrage.magenta.at have known CVE vulnerabilities?

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.

Is umfrage.magenta.at's SSL certificate valid?

Yes. Strengths: Certificate valid, 128 days remaining; Issued by Sectigo Limited.

umfrage.magenta.at Security Report — Grade B- (80/100)

Q: Does umfrage.magenta.at have DMARC configured?

Yes. umfrage.magenta.at's DMARC policy is set to 'none'. SPF record: yes. Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 7/10 (within limit); DKIM configured (selectors: selector1). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Q: Does umfrage.magenta.at have DNSSEC enabled?

No. Strengths: 2 nameservers configured (ns1.t-mobile.at, ns2.t-mobile.at); SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: All nameservers are from a single provider (t-mobile.at) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

B-

Trust rating

Good · 80/100

Procurement snapshot

0 critical findings identified — these point to architectural gaps, not just configuration tweaks.

Strengths

DNS CAA Records

TLS Configuration

TLS Protocol Support

Known Breaches

Questions to ask

Confirm backup mail server configuration

Estimated remediation effort: 1–2 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned August 17, 2026

Score

100 75 50 25 0

B-

umfrage.magenta.at

80/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

Pro subscribers only

ISO 27001

Certificate not on file

3rd party · accredited body

Pro subscribers only

GDPR

DPA not on file

Self-reported

Pro subscribers only

CCPA

Self-reported

Pro subscribers only

Incident History

None in 12 months

March 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

April 2023 – Feb 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

Security Posture

6 items need attention

9 passed

Add 3 missing security headers

Security Headers

1–2 hours

This leaves visitors exposed to attacks like clickjacking and content-type sniffing. umfrage.magenta.at is missing 3 of the 5 security headers browsers use to protect visitors — for example, one stops your site being loaded inside a hidden frame on another site to trick people into clicking things (clickjacking). These are settings, not code changes, so they're usually quick to add. On top of that, 2 of the headers you do have are misconfigured: CSP: 'unsafe-inline' in script directives — negates XSS protection; CSP: 'unsafe-eval' allows eval() — weakens XSS protection.

PCI-DSS 4.0Req 6.4.1

Security headers are required application controls

OWASPSecure Headers

Recommended baseline for web applications

How to fix this

1Add these headers exactly as shown. If you manage your own server (nginx, Apache, IIS) or a CDN like Cloudflare, add it in that config. If your site is on a managed platform (Wix, Squarespace, Shopify, WordPress.com), search their help center for "custom headers" or ask their support — most support it, though a few don't.

X-Frame-Options: SAMEORIGIN

Referrer-Policy: strict-origin-when-cross-origin

Permissions-Policy: camera=(), microphone=(), geolocation=()

2Fix these existing headers — they're present but not doing their job: CSP: 'unsafe-inline' in script directives — negates XSS protection; CSP: 'unsafe-eval' allows eval() — weakens XSS protection. If you manage your own server (nginx, Apache, IIS) or a CDN like Cloudflare, add it in that config. If your site is on a managed platform (Wix, Squarespace, Shopify, WordPress.com), search their help center for "custom headers" or ask their support — most support it, though a few don't.

3Confirm it worked: search "http header checker" and enter umfrage.magenta.at — check the headers below in the response.

Security headers guide

Report unlocked.

View all 9 passed checks

DNS CAA Records

TLS Configuration

TLS Protocol Support

Known Breaches

HSTS Header

Cookie Security

Certificate Hygiene

CVE Exposure

Subprocessors & Tech Stack

Company Signals

Claim profile →

Operational risk

Low

11 yrs operating. Well-funded

Lynxradar · Composite signal

Last funding

$40B

Series F · Mar 2025 · SoftBank-led

Crunchbase ↗

Employees

~3,000

+40% YoY growth

LinkedIn ↗

Trust Resources

Claim profile →

Trust Center

trust.umfrage.magenta.at ↗

Security page

umfrage.magenta.at/security ↗

umfrage.magenta.at/privacy ↗

DPA (Data Processing Agreement)

umfrage.magenta.at/dpa ↗

Updated recently

Subprocessors List

umfrage.magenta.at/policies/subprocessors ↗

Similar companies

Appears in

Claim profile →

SOC 2 Type II certified vendors

847 companies · Updated weekly by LynxRadar

Track

ISO 27001 certified SaaS

312 companies · Updated weekly by LynxRadar

Track

Top AI vendors by trust score

94 companies · LynxRadar ranking

Track

Enterprise-ready SaaS · Trust score A or above

203 companies · LynxRadar ranking

Track

Blocking Issues

2/5 present

Missing: X-Frame-Options, Referrer-Policy, Permissions-Policy

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Warn

Strengths: Mail handled by Microsoft 365; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆

Warn

Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 2 nameservers configured (ns1.t-mobile.at, ns2.t-mobile.at); SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: All nameservers are from a single provider (t-mobile.at) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

p=none

Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 7/10 (within limit); DKIM configured (selectors: selector1). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Best Practice

Warn

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.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆