Hardenize Logo

Public Report | web.de

TEST ANOTHER

web.de

17 Oct 2026 15:30 UTC

Domain Name System

DNS Zonegood
DNS Recordsgood
DNSSECgood
CAAgood

Email

Mail serversIncomplete
TLSIncomplete
CertificatesIncomplete
MTA-STSwarning
TLS-RPTgood
DANEIncomplete
SPFgood
DMARCgood

WWW

HTTP (80)good
HTTPS (443)good
TLSgood
Certificatesgood
Cookieswarning
HTML Contentgood
Strict Transport Securitygood
Content Security Policygood
Subresource Integrityneutral
Frame Optionsgood
XSS Protectiongood
Content Type Optionsgood
Web Security Overview
Warning
HTTPS

Web sites need to use encryption to help their visitors know they're in the right place, as well as provide confidentiality and content integrity. Sites that don't support HTTPS may expose sensitive data and have their pages modified and subverted.
There are issues with this site's HTTPS configuration.

For all sites VERY IMPORTANT medium EFFORT
Supported and well configured
HTTPS Redirection

To deploy HTTPS properly, web sites must redirect all unsafe (plaintext) traffic to the encrypted variant. This approach ensures that no sensitive data is exposed and that further security technologies can be activated.

For all sites VERY IMPORTANT low EFFORT
Supported and well configured
HTTP Strict Transport Security

HTTP Strict Transport Security (HSTS) is an HTTPS extension that instructs browsers to remember sites that use encryption and enforce strict security requirements. Without HSTS, active network attacks are easy to carry out.

For important sites VERY IMPORTANT medium EFFORT
Supported and well configured
HSTS Preloaded

HSTS Preloading is informing browsers in advance about a site's use of HSTS, which means that strict security can be enforced even on the first visit. This approach provides best HTTPS security available today.

For important sites VERY IMPORTANT medium EFFORT
Supported and well configured
Content Security Policy

Content Security Policy (CSP) is an additional security layer that enables web sites to control browser behavior, creating a safety net that can counter attacks such as cross-site scripting.

For important sites IMPORTANT high EFFORT
Email Security Overview
Unable to determine
STARTTLS

All hosts that receive email need encryption to ensure confidentiality of email messages. Email servers thus need to support STARTTLS, as well as provide decent TLS configuration and correct certificates.
Unable to determine STARTTLS status.

For all sites VERY IMPORTANT low EFFORT
Supported and well configured
SPF

Sender Policy Framework (SPF) enables organizations to designate servers that are allowed to send email messages on their behalf. With SPF in place, spam is easier to identify.

For important sites IMPORTANT low EFFORT
Supported and well configured
DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a mechanism that allows organizations to specify how unauthenticated email (identified using SPF and DKIM) should be handled.

For important sites IMPORTANT low EFFORT

DNS Zone

The global DNS infrastructure is organized as a series of hierarchical DNS zones. The root zone hosts a number of global and country TLDs, which in turn host further zones that are delegated to their customers. Each organization that controls a zone can delegate parts of its namespace to other zones. In this test we perform detailed inspection of a DNS zone, but only if the host being tested matches the zone.

Test passed
Everything seems to be well configured. Well done.

Nameserver Names

Nameservers can be referred to by name and by address. In this section we show the names, which can appear in the NS records, the referrals from the parent zone, and the SOA record. In some situations, servers from the parent zone respond authoritatively, in which case we will include them in the list as well.

Nameserver Operational IPv4 IPv6 Sources
ns-webde.ui-dns.biz.
185.132.33.198
217.160.81.198
2001:8d8:fe:53:0:d9a0:51c6:100
2607:f1c0:fe:53:185:132:33:198 		The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. REFERRAL NS
ns-webde.ui-dns.com.
185.132.34.198
217.160.82.198
2001:8d8:fe:53:0:d9a0:52c6:100
2607:f1c0:fe:53:185:132:34:198 		The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. REFERRAL NS
ns-webde.ui-dns.de. PRIMARY
185.132.32.198
217.160.80.198
2001:8d8:fe:53:0:d9a0:50c6:100
2607:f1c0:fe:53:185:132:32:198 		The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. REFERRAL SOA NS
ns-webde.ui-dns.org.
185.132.35.198
217.160.83.198
2001:8d8:fe:53:0:d9a0:53c6:100
2607:f1c0:fe:53:185:132:35:198 		The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. REFERRAL NS

Nameserver Addresses

This section shows the configuration of all discovered nameservers by their IP address. To find all applicable nameservers, we inspect the parent zone nameservers for names and glue and then the tested zone nameservers for NS records. We then resolve all discovered names to IP addresses. Finally, we test each address individually.

Nameserver Operational Authoritative Recursive UDP TCP Sources Payload Size
185.132.32.198 PRIMARY
ns-webde.ui-dns.de.
PTR: ns-webde.ui-dns.de. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
185.132.33.198
ns-webde.ui-dns.biz.
PTR: ns-webde.ui-dns.biz. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
185.132.34.198
ns-webde.ui-dns.com.
PTR: ns-webde.ui-dns.com. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
185.132.35.198
ns-webde.ui-dns.org.
PTR: ns-webde.ui-dns.org. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
217.160.80.198 PRIMARY
ns-webde.ui-dns.de.
PTR: ns-webde.ui-dns.de. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
217.160.81.198
ns-webde.ui-dns.biz.
PTR: ns-webde.ui-dns.biz. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
217.160.82.198
ns-webde.ui-dns.com.
PTR: ns-webde.ui-dns.com. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
217.160.83.198
ns-webde.ui-dns.org.
PTR: ns-webde.ui-dns.org. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
2001:8d8:fe:53:0:d9a0:50c6:100 PRIMARY
ns-webde.ui-dns.de.
PTR: ns-webde.ui-dns.de. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
2001:8d8:fe:53:0:d9a0:51c6:100
ns-webde.ui-dns.biz.
PTR: ns-webde.ui-dns.biz. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
2001:8d8:fe:53:0:d9a0:52c6:100
ns-webde.ui-dns.com.
PTR: ns-webde.ui-dns.com. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
2001:8d8:fe:53:0:d9a0:53c6:100
ns-webde.ui-dns.org.
PTR: ns-webde.ui-dns.org. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
2607:f1c0:fe:53:185:132:32:198 PRIMARY
ns-webde.ui-dns.de.
PTR: ns-webde.ui-dns.de. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
2607:f1c0:fe:53:185:132:33:198
ns-webde.ui-dns.biz.
PTR: ns-webde.ui-dns.biz. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
2607:f1c0:fe:53:185:132:34:198
ns-webde.ui-dns.com.
PTR: ns-webde.ui-dns.com. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220
2607:f1c0:fe:53:185:132:35:198
ns-webde.ui-dns.org.
PTR: ns-webde.ui-dns.org. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1220

Start of Authority (SOA) Record

Start of Authority (SOA) records contain administrative information pertaining to one DNS zone, especially the configuration that's used for zone transfers between the primary nameserver and the secondaries. Only one SOA record should exist, with all nameservers providing the same information.

The domain name of the primary nameserver for the zone. Also known as MNAME.Primary nameserver ns-webde.ui-dns.de.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email dnsadmin.1und1.de.
Zone serial or version number.Serial number 2005105908
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval 28,800 seconds (about 8 hours)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval 7,200 seconds (about 2 hours)
The length of time after which secondary nameservers should stop responding to queries for a zone, assuming no updates were obtained from the primary.Expire interval 604,800 seconds (about 7 days)
TTL for purposes of negative response caching. Negative cache TTL 600 seconds (about 10 minutes)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL 40,000 seconds (about 11 hours 6 minutes)

Analysis

Good
No problems detected with the zone configuration
Excellent. This DNS zone is in a good working order. No problems detected.

Backing DNS Queries

Below are all DNS queries we submitted during the zone inspection.

ID Server Transport Question Name Type Status

DNS Records

Correctly functioning name servers are necessary to hold and distribute information that's necessary for your domain name to operate correctly. Examples include converting names to IP addresses, determining where email should go, and so on. More recently, the DNS is being used to communicate email and other security policies.

Test passed
Everything seems to be well configured. Well done.

DNS Records

These are the results of individual DNS queries against your nameserver for common resource record types.

Name TTL Type Data
web.de.     300 A 217.72.199.68            
www.web.de.     300 A 217.72.199.68            
web.de.     40000 CAA 0 issuewild "digicert.com"            
web.de.     40000 CAA 0 issue "telesec.de"            
web.de.     40000 CAA 0 issuewild "sectigo.com"            
web.de.     40000 CAA 0 issue "sectigo.com"            
web.de.     40000 CAA 0 issuewild "telesec.de"            
web.de.     40000 CAA 0 issue "Digicert.com"            
web.de.     600 DNSKEY 257 3 8 AwEAAcBs30zgmOeYcUYzJetRzRYGQXlnXpv2gO3KWf5BYRn9OqFtUBzFOqO16Ow2XPqR8SWqpAVpnToQICICZyf58SHaefGn94fTj+PlwJi4HhoCbim2U3G5sYtl5xoNfUCaDXDQFJp+HnZlaA9afHutOVFtqCmMHV+2ApSyOFFETQNmq4YoxLxiJoxSjvQAaaiJKVoA4wykjXALMyCmbXGH4aMVbW2m0Fuqe+nKU8myW14nCASBo0mDO6cBNsBwu7IiL4SxxnflDCSTkn/FnCKtzf7aVzzrRM4SqTe4NOm7wPmCZiAGoxOL15PZ7YQSt9BEXU6gMdGxCGVBdtgM13NfziM=            
web.de.     600 DNSKEY 256 3 8 AwEAAcXRpr9APbDArCZLvkbCbyJztg7B3a1MAQ2E6xI7muXi5RK8IRM3UM9Yns74jDDPCzDlm8drhZ+jmvNR0i7pa6+1IrTLYRXLMtI4vtIrhwKyruS2+6foA593crKvimzS578gQ/lc3BKILY/tQWYbytOoBi9hQj+FlpdpX6XshUmk+nibHyAqpyfCUFc8Wq4X/sLwvt+HEOLDNOPl2fiB3vbXCa7r/HOR9cOEztKSIi8szqB/rzhmtEOO+HZpj5oFLcFv4O/V19HCqmCGUHMyOaFRBJKWD+qlO91xEXKqKo2ecTpuIzuBFlyzC3cQRWpgsq8nkuIilvEgJq36Ucvzxcs=            
web.de.     7200 MX 100 mx-ha03.web.de.            
web.de.     7200 MX 100 mx-ha02.web.de.            
web.de.     40000 NS ns-webde.ui-dns.org.            
web.de.     40000 NS ns-webde.ui-dns.com.            
web.de.     40000 NS ns-webde.ui-dns.biz.            
web.de.     40000 NS ns-webde.ui-dns.de.            
web.de.     600 SOA ns-webde.ui-dns.de. dnsadmin.1und1.de. 2005105908 28800 7200 604800 600            
web.de.     40000 TXT "google-site-verification=4kOTEODoJ0gf-gR71erruc56vEPOpyAuppJRHNC-hk0"            
web.de.     3600 TXT "v=spf1 redirect=_spf.web.de"            
web.de.     40000 TXT "kqpx82j1ql9zhqh54gdr8pj9f1ytvht1"            
web.de.     300 TXT "google-site-verification=uHSKas5L2d4qGiqXVFuwvgu-In8Byl7dJXmTSLcOJuY"            
web.de.     40000 TXT "mindmanager-verification=1ea2fdbe5379cc0f8cfe95fa5ecfdc1ff943a7bd015aed8afb5717dad146adac"            
web.de.     300 TXT "facebook-domain-verification=ksd7xc6g15rm7xkdga4qcm9hasgkny"            
web.de.     40000 TXT "_cddkhzzdq16uacbk5ilv3giqg9evcti"            
web.de.     300 TXT "g6ftbncmryg0y6h956jfd242s1z9tndk"            
web.de.     40000 TXT "dzd5thdqpcp7f5d2p8l4vj5m5wdt21cs"            
web.de.     300 TXT "Trustpilot-Verification-kqvVskCm6JQ9Vg1qAmahpBSJ5tvZORbriFyVIk4E"            
web.de.     40000 TXT "google-site-verification=No4jlUg2OIV7IsI2UF0v792Q8HgI9Brnp7qary1nMAQ"            
_dmarc.web.de.     300 TXT "v=DMARC1; p=quarantine; rua=mailto:dmarcreport@web.de"            
_mta-sts.web.de.     40000 TXT "v=STSv1;id=20180928194800Z;"            
_smtp._tls.web.de.     40000 TXT "v=TLSRPTv1;rua=mailto:smtp-tlsrpt@1und1.de"            

Backing DNS Queries

Below are all DNS queries we submitted while inspecting the resource records.

ID Server Question Name Type Status

DNSSEC

DNSSEC is an extension of the DNS protocol that provides cryptographic assurance of the authenticity and integrity of responses; it's intended as a defense against network attackers who are able to manipulate DNS to redirect their victims to servers of their choice. DNSSEC is controversial, with the industry split largely between those who think it's essential and those who believe that it's problematic and unnecessary.

Test passed
Everything seems to be well configured. Well done.

Analysis

Good
DNSSEC is well configured
Good. This domain name has well-configured DNSSEC.

Useful DNSSEC Tools

Certification Authority Authorization

CAA (RFC 8659) is a new standard that allows domain name owners to restrict which CAs are allowed to issue certificates for their domains. This can help to reduce the chance of misissuance, either accidentally or maliciously. In September 2017, CAA became mandatory for CAs to implement.

Test passed
Everything seems to be well configured. Well done.

CAA Policy Information

The DNS hostname where this policy is located.Policy host web.de
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.issue 		telesec.de  flags: 0
The issuewild property has the same syntax and semantics as
the issue property except that issuewild properties only grant
authorization to issue certificates that specify a wildcard domain
and issuewild properties take precedence over issue properties when
specified.issuewild 		telesec.de  flags: 0
The issuewild property has the same syntax and semantics as
the issue property except that issuewild properties only grant
authorization to issue certificates that specify a wildcard domain
and issuewild properties take precedence over issue properties when
specified.issuewild 		digicert.com  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.issue 		Digicert.com  flags: 0
The issuewild property has the same syntax and semantics as
the issue property except that issuewild properties only grant
authorization to issue certificates that specify a wildcard domain
and issuewild properties take precedence over issue properties when
specified.issuewild 		sectigo.com  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.issue 		sectigo.com  flags: 0

Analysis

Powerup!
Issuance of S/MIME certificates not restricted
This policy doesn't restrict the issuance of S/MIME certificates. Consider using the `issuemail` directive to restrict which CAs, if any, can issue.
Powerup!
Issuance of BIMI not restricted
This policy doesn't restrict issuance of BIMI certificates. Consider using the `issuevmc` directive to restrict which CAs, if any, can issue.
Good
CAA policy restricts issuance
Great. This domain name uses CAA to restrict which CAs are allowed to issue certificates for it.
Powerup!
Policy doesn't use reporting
This policy doesn't use reporting, which means that there is no way to contact you when a violation is detected. The CAA RFC defines the iodef property that can be used for this purpose. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

Email (SMTP)

An internet hostname can be served by zero or more mail servers, as specified by MX (mail exchange) DNS resource records. Each server can further resolve to multiple IP addresses, for example to handle IPv4 and IPv6 clients. Thus, in practice, hosts that wish to receive email reliably are supported by many endpoint.

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.
Server Preference Operational STARTTLS TLS PKI DNSSEC DANE
mx-ha03.web.de
212.227.15.154
PTR: mx-ha03.web.de		 100 
554-web.de (mxweb004) Nemesis ESMTP Service not available
554-No SMTP service
554-Bad DNS PTR resource record.
554 For explanation visit https://postmaster.web.de/en/case?c=r0601&i=ip&v=34.48.223.206&r=1MgNYp-1wgpba076F-00hrra
QUIT
Unable to determine as the SMTP server
won't accept our connection. 		Unable to determine as the SMTP server
won't accept our connection. 		Unable to determine as the SMTP server
won't accept our connection. 		Unable to determine as the SMTP server
won't accept our connection.
mx-ha02.web.de
212.227.15.138
PTR: mx-ha02.web.de		 100 
554-web.de (mxweb104) Nemesis ESMTP Service not available
554-No SMTP service
554-Bad DNS PTR resource record.
554 For explanation visit https://postmaster.web.de/en/case?c=r0601&i=ip&v=34.48.223.206&r=1MgNYj-1wgpbZ07Ml-00hsNz
QUIT
Unable to determine as the SMTP server
won't accept our connection. 		Unable to determine as the SMTP server
won't accept our connection. 		Unable to determine as the SMTP server
won't accept our connection. 		Unable to determine as the SMTP server
won't accept our connection.

Analysis

Warning
Network access blocked
One or more tests in this section couldn't complete because network access was blocked. This usually happens when there are rate limiting controls in place. SMTP servers are often very sensitive and refuse access at the slightest dislike of the client.

Error message: Blocked

Email TLS (SMTP)

Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

Analysis

Notice
Sensitive SMTP domain
During the report we encountered one or more SMTP servers that are known to enforce strict rate access controls. We haven't tested those servers because we are unable to complete the TLS analysis in a timely manner. In the future we will test such servers as a background activity. The information we show for the SMTP servers may not be accurate. For example, some servers do not offer STARTTLS to blacklisted clients.

Email Certificates (SMTP)

A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

Analysis

Notice
Sensitive SMTP domain
During the report we encountered one or more SMTP servers that are known to enforce strict rate access controls. We haven't tested those servers because we are unable to complete the TLS analysis in a timely manner. In the future we will test such servers as a background activity. The information we show for the SMTP servers may not be accurate. For example, some servers do not offer STARTTLS to blacklisted clients.

Email DANE (SMTP)

DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

Analysis

Notice
Sensitive SMTP domain
During the report we encountered one or more SMTP servers that are known to enforce strict rate access controls. We haven't tested those servers because we are unable to complete the TLS analysis in a timely manner. In the future we will test such servers as a background activity. The information we show for the SMTP servers may not be accurate. For example, some servers do not offer STARTTLS to blacklisted clients.

SPF

Sender Policy Framework (SPF) is a protocol that allows domain name owners to control which internet hosts are allowed to send email on their behalf. This simple mechanism can be used to reduce the effect of email spoofing and cut down on spam.

Test passed
Everything seems to be well configured. Well done.

SPF Policy Information Main policy

Host where this policy is located.Location web.de
SPF version used by this policy.v spf1
This modifier is intended for consolidating both
authorizations and policy into a common set to be
shared within a single administrative domain. redirect 		_spf.web.de

Analysis

Info
SPF policy found

Policy text: v=spf1 redirect=_spf.web.de

Location: web.de

Good
SPF policy is valid
Good. Your SPF policy is syntactically valid.
Good
Policy DNS lookups under limit
Good. Your policy stays under the limit of up to 10 DNS queries. The SPF specification Section 4.6.4. requires implementations to limit the total number of DNS queries. Policies that exceed the limit should not be used and may not work in practice.

Lookups: 6

SPF Policy Information Included policy

Host where this policy is located.Location _spf.web.de
SPF version used by this policy.v spf1
This mechanism matches if the sending IP address
is one of the IP addresses that belong to the target
domain name. Matches both IPv4 and IPv6 addresses. a 		mout.web.de
This mechanism matches if the sending IP address
is one of the IP addresses that belong to the target
domain name. Matches both IPv4 and IPv6 addresses. a 		mout-xforward.web.de
This mechanism matches if the sending IP address
is one of the IP addresses that belong to the target
domain name. Matches both IPv4 and IPv6 addresses. a 		mout-bounce.web.de
This mechanism matches if the sending IP address
is one of the IP addresses that belong to the target
domain name. Matches both IPv4 and IPv6 addresses. a 		mout-csbulk.1and1.com
This mechanism matches if the sending IP address
is one of the IP addresses that belong to the target
domain name. Matches both IPv4 and IPv6 addresses. a 		mout-cscorp.1and1.com
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms. ~all

DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a scalable mechanism by which a mail-originating organization can express domain-level policies and preferences for message validation, disposition, and reporting, that a mail-receiving organization can use to improve mail handling.

Test passed
Everything seems to be well configured. Well done.

DMARC Policy Information

The location from which we obtained this policy.Policy location _dmarc.web.de
DMARC version used by this policy.v DMARC1
Indicates the policy to be enacted by the receiver at
the request of the domain owner. Possible values are:
none, quarantine, and reject.p 		quarantine
Addresses to which aggregate feedback is to be sent.rua mailto:dmarcreport@web.de

Analysis

Info
DMARC policy found

Policy: v=DMARC1; p=quarantine; rua=mailto:dmarcreport@web.de

Host: _dmarc.web.de

Good
Policy is valid
Good. You have a valid DMARC policy.

MTA Strict Transport Security

SMTP Mail Transfer Agent Strict Transport Security (MTA-STS) is a mechanism enabling mail service providers to declare their ability to receive Transport Layer Security (TLS) secure SMTP connections, and to specify whether sending SMTP servers should refuse to deliver to MX hosts that do not offer TLS with a trusted server certificate.

Test passed, but there are warnings
Some aspect of your site's configuration require your attention.

MTA-STS Policy Indicator

Location from which we retrieved the policy indicator.Location _mta-sts.web.de
MTA-STS standard version used by this policy indicator.Version STSv1
Unique policy identifier, whose value must change
every time the underlying policy changes.ID 		20180928194800Z

Analysis

Good
MTA-STS policy indicator valid
Good. Your MTA-STS policy indicator is valid.

MTA-STS Policy

The URL from which the policy was obtained.Location https://mta-sts.web.de/.well-known/mta-sts.txt
Policy standard version.version STSv1
Policy duration, which specifies how long the sending
MTAs should remember and enforce the server policy for.max‑age 		604,800 seconds (about 7 days)
Policy mode, which can be one of 'none', 'testing' and
'enforcing'. Guess which is best! :)mode 		testing
One 'mx' directive specifies one email server
pattern that's allowed for this host.mx 		mx-ha02.web.de
One 'mx' directive specifies one email server
pattern that's allowed for this host.mx 		mx-ha03.web.de

Analysis

Good
Policy host certificate is valid
Good. Your MTA-STS policy is delivered via a web server that has a valid publicly trusted certificate. This is a necessary condition for the policy to be recognized.
Notice
Policy HTTPS response information

Status code: 200

Length: 83 bytes

Content-Type: text/plain

Warning
Policy deployed in testing mode
The MTA-STS policy is deployed in testing mode, which does not enforce strict transport security and may not provide full protection.
Good
MTA-STS policy is valid
Good. Your MTA-STS policy is valid.

Certificate: mta-sts.web.de

Leaf certificate mta-sts.gmx.net
Issuer: Deutsche Telekom Security GmbH
Not Before: 17 Aug 2026 09:34:25 UTC
Not After: 02 Mar 2027 23:59:59 UTC (expires in 4 months 13 days)
Key: RSA 3072 bits
Signature: SHA256withRSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Good
Certificate satisfies Apple's CT compliance requirements
Good. This certificate satisfies Apple's CT requirements at present.

Certificate Chain

Leaf certificate
mta-sts.gmx.net | 3bf61d7
Not After: 02 Mar 2027 23:59:59 UTC (expires in 4 months 13 days)
Authentication: RSA 3072 bits (SHA256withRSA)
 View details
Intermediate certificate
Telekom Security OV RSA CA 26A | c76e23d
Not After: 18 Mar 2029 23:59:59 UTC (expires in 2 years 5 months)
Authentication: RSA 4096 bits (SHA384withRSA)
 View details
Intermediate certificate
Telekom Security TLS RSA Root 2023 | 6306c49
Not After: 30 Sep 2033 23:59:59 UTC (expires in 6 years 11 months)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Root certificate
T-TeleSec GlobalRoot Class 3 | fd73dad
Not After: 01 Oct 2033 23:59:59 UTC (expires in 6 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details

Analysis

Good
Certificate chain is correct
Good. This chain contains all the right certificates and in the right order.

SMTP TLS Reporting

SMTP TLS Reporting (RFC 8460), or TLS-RPT for short, describes a reporting mechanism and format by which systems sending email can share statistics and specific information about potential failures with recipient domains. Recipient domains can then use this information to both detect potential attacks and diagnose unintentional misconfigurations. TLS-RPT can be used with DANE or MTA-STS.

Test passed
Everything seems to be well configured. Well done.

TLS-RPT Policy

Location from which we retrieved the policy indicator.Location _smtp._tls.web.de
TLS-RPT standard version used by this policy indicator.Version TLSRPTv1
Reporting endpoints specified in the policy.Reporting Endpoints mailto:smtp-tlsrpt@1und1.de

Analysis

Good
SMTP TLS-RPT policy valid
Good. Your TLS-RPT policy is valid. SMTP TLS Reporting is a young standard that is not yet widely supported, but support is probably going to increase over time.

HTTP (80)

To observe your HTTP implementation, we submit a request to the homepage of your site on port 80, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers.

Test passed
Everything seems to be well configured. Well done.

URL: http://web.de/

1
http://web.de/
HTTP/1.1 301 Moved Permanently
2
https://web.de/
HTTP/1.1 200 OK

Analysis

Good
HTTP redirects to HTTPS
Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.web.de/

1
http://www.web.de/
HTTP/1.1 301 Moved Permanently
2
https://www.web.de/
HTTP/1.1 301 Moved Permanently
3
https://web.de/
HTTP/1.1 200 OK

Analysis

Good
HTTP redirects to HTTPS
Good. This plaintext HTTP server redirects to HTTPS.

HTTP (443)

To observe your HTTPS implementation, we submit a request to the homepage of your site on port 443, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers. We use the most recent set of headers returned from the tested hostname for further tests such as HSTS and HPKP.

Test passed
Everything seems to be well configured. Well done.

URL: https://web.de/

1
https://web.de/
HTTP/1.1 200 OK

URL: https://www.web.de/

1
https://www.web.de/
HTTP/1.1 301 Moved Permanently
2
https://web.de/
HTTP/1.1 200 OK

WWW TLS

Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.

Test passed
Everything seems to be well configured. Well done.

TLS Configuration: web.de (217.72.199.68)

Encryption protocol version determines what features are
available for negotiation between client and server.Supported protocols 		TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference 		Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: X25519MLKEM768
Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_CHACHA20_POLY1305_SHA256  256 bits (Hybrid PQ 9472 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: X25519MLKEM768
Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_AES_128_GCM_SHA256  128 bits (Hybrid PQ 9472 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: X25519MLKEM768
Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_AES_256_GCM_SHA384  256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference 		Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256  256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256  128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Only strong suites supported
Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Good
All TLS connections with this server satisfy Chrome's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Good
Post-quantum key exchange supported
Excellent. This server supports post-quantum cryptography (PQC) and uses it for key exchange. PQC is still in the process of being standardized and deployed. Protecting the key exchange against future quantum computers is considered to be one of the more pressing tasks.

Algorithm: X25519MLKEM768

Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.web.de (217.72.199.68)

Encryption protocol version determines what features are
available for negotiation between client and server.Supported protocols 		TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference 		Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: X25519MLKEM768
Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_CHACHA20_POLY1305_SHA256  256 bits (Hybrid PQ 9472 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: X25519MLKEM768
Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_AES_128_GCM_SHA256  128 bits (Hybrid PQ 9472 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: X25519MLKEM768
Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_AES_256_GCM_SHA384  256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference 		Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256  256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256  128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Only strong suites supported
Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Good
All TLS connections with this server satisfy Chrome's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Good
Post-quantum key exchange supported
Excellent. This server supports post-quantum cryptography (PQC) and uses it for key exchange. PQC is still in the process of being standardized and deployed. Protecting the key exchange against future quantum computers is considered to be one of the more pressing tasks.

Algorithm: X25519MLKEM768

Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

WWW Certificates

A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.

Test passed
Everything seems to be well configured. Well done.

Certificate: web.de

Leaf certificate *.web.de
Issuer: Deutsche Telekom Security GmbH
Not Before: 17 Aug 2026 10:15:37 UTC
Not After: 02 Mar 2027 23:59:59 UTC (expires in 4 months 13 days)
Key: RSA 3072 bits
Signature: SHA256withRSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Good
Certificate satisfies Apple's CT compliance requirements
Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate
*.web.de | e311ab3
Not After: 02 Mar 2027 23:59:59 UTC (expires in 4 months 13 days)
Authentication: RSA 3072 bits (SHA256withRSA)
 View details
Intermediate certificate
Telekom Security OV RSA CA 26A | c76e23d
Not After: 18 Mar 2029 23:59:59 UTC (expires in 2 years 5 months)
Authentication: RSA 4096 bits (SHA384withRSA)
 View details
Intermediate certificate
Telekom Security TLS RSA Root 2023 | 6306c49
Not After: 30 Sep 2033 23:59:59 UTC (expires in 6 years 11 months)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Root certificate
T-TeleSec GlobalRoot Class 3 | fd73dad
Not After: 01 Oct 2033 23:59:59 UTC (expires in 6 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details

Analysis

Good
Certificate chain is correct
Good. This chain contains all the right certificates and in the right order.

Certificate: www.web.de

Leaf certificate *.web.de
Issuer: Deutsche Telekom Security GmbH
Not Before: 17 Aug 2026 10:15:37 UTC
Not After: 02 Mar 2027 23:59:59 UTC (expires in 4 months 13 days)
Key: RSA 3072 bits
Signature: SHA256withRSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Good
Certificate satisfies Apple's CT compliance requirements
Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate
*.web.de | e311ab3
Not After: 02 Mar 2027 23:59:59 UTC (expires in 4 months 13 days)
Authentication: RSA 3072 bits (SHA256withRSA)
 View details
Intermediate certificate
Telekom Security OV RSA CA 26A | c76e23d
Not After: 18 Mar 2029 23:59:59 UTC (expires in 2 years 5 months)
Authentication: RSA 4096 bits (SHA384withRSA)
 View details
Intermediate certificate
Telekom Security TLS RSA Root 2023 | 6306c49
Not After: 30 Sep 2033 23:59:59 UTC (expires in 6 years 11 months)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Root certificate
T-TeleSec GlobalRoot Class 3 | fd73dad
Not After: 01 Oct 2033 23:59:59 UTC (expires in 6 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details

Analysis

Good
Certificate chain is correct
Good. This chain contains all the right certificates and in the right order.

DANE (443)

DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Cookies

Cookies are small chunks of text that are sent between your browser and a website. They are often essential to the operation of the site and sometimes contain sensitive information. Session cookies sent from secure sites must be explicitly marked as secure to prevent being obtained by active network attackers.

Test passed, but there are warnings
Some aspect of your site's configuration require your attention.

HTTP Cookie: SSLB

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.Value 		.0
Cookie domain. When domain is implied (not explicitly set in a cookie),
most browsers (but not IE) treat the cookie as host-only, meaning that
no other server can overwrite it.Domain 		web.de
Cookie path. This field can't be used as security measure,
but it could be of use to avoid cookie name collision
in non-adversarial contexts.Path 		/
The HttpOnly flag prevents the cookie from being accessed
from JavaScript, thus making them more difficult
to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie
should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site,
it sends all associated cookies. This is not always
desirable, because it might allow third-party sites
to perform site actions under the identity of the user.
This attack is known as Cross-Site Request Forgery.
With SameSite cookies (still in development, but already
supported in some browsers), you can choose to be more
strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Warning
Cookie is not secure
This cookie, which has been sent over an encrypted channel, doesn't have the secure flag set. As a result, an active network attacker can easily recover it.

HTTP Cookie: SSLB

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.Value 		.0
Cookie domain. When domain is implied (not explicitly set in a cookie),
most browsers (but not IE) treat the cookie as host-only, meaning that
no other server can overwrite it.Domain 		web.de
Cookie path. This field can't be used as security measure,
but it could be of use to avoid cookie name collision
in non-adversarial contexts.Path 		/
The HttpOnly flag prevents the cookie from being accessed
from JavaScript, thus making them more difficult
to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie
should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site,
it sends all associated cookies. This is not always
desirable, because it might allow third-party sites
to perform site actions under the identity of the user.
This attack is known as Cross-Site Request Forgery.
With SameSite cookies (still in development, but already
supported in some browsers), you can choose to be more
strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Warning
Cookie is not secure
This cookie, which has been sent over an encrypted channel, doesn't have the secure flag set. As a result, an active network attacker can easily recover it.

HTTP Cookie: ui_cid

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.Value 		OPTOUT
Cookie domain. When domain is implied (not explicitly set in a cookie),
most browsers (but not IE) treat the cookie as host-only, meaning that
no other server can overwrite it.Domain 		Implied (web.de)
Cookie path. This field can't be used as security measure,
but it could be of use to avoid cookie name collision
in non-adversarial contexts.Path 		/
Cookies are designed to always expire. Session cookies
are truly ephemeral and remain cached until the browser
is closed. The Expires and Max-Age cookie attributes can
be used to specify that a cookie should stay alive for
longer.Expires 		Sun Oct 17 15:30:20 UTC 2027 (11 months 29 days)
The HttpOnly flag prevents the cookie from being accessed
from JavaScript, thus making them more difficult
to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie
should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site,
it sends all associated cookies. This is not always
desirable, because it might allow third-party sites
to perform site actions under the identity of the user.
This attack is known as Cross-Site Request Forgery.
With SameSite cookies (still in development, but already
supported in some browsers), you can choose to be more
strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Good
Cookie is secure
Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: allin_segment

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.Value 		2
Cookie domain. When domain is implied (not explicitly set in a cookie),
most browsers (but not IE) treat the cookie as host-only, meaning that
no other server can overwrite it.Domain 		web.de
Cookie path. This field can't be used as security measure,
but it could be of use to avoid cookie name collision
in non-adversarial contexts.Path 		/
Cookies are designed to always expire. Session cookies
are truly ephemeral and remain cached until the browser
is closed. The Expires and Max-Age cookie attributes can
be used to specify that a cookie should stay alive for
longer.Expires 		Fri Jan 15 15:30:20 UTC 2027 (2 months 28 days)
The HttpOnly flag prevents the cookie from being accessed
from JavaScript, thus making them more difficult
to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie
should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site,
it sends all associated cookies. This is not always
desirable, because it might allow third-party sites
to perform site actions under the identity of the user.
This attack is known as Cross-Site Request Forgery.
With SameSite cookies (still in development, but already
supported in some browsers), you can choose to be more
strict. The possible values are 'lax' and 'strict'.SameSite 		lax

Analysis

Good
Cookie is secure
Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: euconsent-bypass

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.Value 		1792251019
Cookie domain. When domain is implied (not explicitly set in a cookie),
most browsers (but not IE) treat the cookie as host-only, meaning that
no other server can overwrite it.Domain 		web.de
Cookie path. This field can't be used as security measure,
but it could be of use to avoid cookie name collision
in non-adversarial contexts.Path 		/
Cookies are designed to always expire. Session cookies
are truly ephemeral and remain cached until the browser
is closed. The Expires and Max-Age cookie attributes can
be used to specify that a cookie should stay alive for
longer.Expires 		Sat Oct 17 17:30:20 UTC 2026 (1 hour 59 minutes)
The HttpOnly flag prevents the cookie from being accessed
from JavaScript, thus making them more difficult
to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie
should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site,
it sends all associated cookies. This is not always
desirable, because it might allow third-party sites
to perform site actions under the identity of the user.
This attack is known as Cross-Site Request Forgery.
With SameSite cookies (still in development, but already
supported in some browsers), you can choose to be more
strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Good
Cookie is secure
Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTML Content

On virtually all web sites, HTML markup, images, style sheets, JavaScript, and other page resources arrive not only over multiple connections but possibly from multiple servers and sites spread across the entire Internet. For a page to be properly encrypted, it’s necessary that all the content is retrieved over HTTPS. In practice, that’s very often not the case, leading to mixed content security problems.

Test passed
Everything seems to be well configured. Well done.

Encryption of Embedded Resources

In this section we look at the transport security of all embedded resources. Mixed active content occurs when there are unprotected scripts or styles embedded in a page. This is typically not allowed by modern browsers. Mixed passive content (images, videos and such) are typically allowed, but shouldn't be present.

6 script(s)
  6 out of 6 are secure  View all
1 CSS file(s)
  1 out of 1 are secure  View all
0 media file(s)
  0 out of 0 are secure

Encryption of Outbound Links

Ideally, an encrypted page should only have links that lead to other encrypted pages. If plaintext links are used, passive network attackers can see where people go after they visit your web site. It's also possible that some sensitive information is leaked in the Referer header.

46 link(s)
  46 out of 46 are encrypted  View all

HTTP Strict Transport Security

HTTP Strict Transport Security (HSTS) vastly improves security of the network encryption layer. With HSTS enabled, browsers no longer allow clicking through certificate warnings errors, which are typically trivial to exploit. Additionally, they will no longer submit insecure (plaintext) requests to the site in question, even if asked.

Test passed
Everything seems to be well configured. Well done.

HSTS Policy  Main host

URL from which this policy was obtained.Location https://www.web.de/
Specifies policy duration. Once activated, HSTS stays in force
until this time lapses. Browsers update policy cache duration
every time they receive a new HSTS header from a site.max‑age 		31,536,000 seconds (about 1 year)
When present, this directive forces HSTS activation
on allsubdomains. For best security, HSTS should be
deployed on the bare domain name (e.g., example.com)
and all its subdomains.includeSubDomains
Presence of this directive indicates that a web site wishes to
permanently use HSTS and that its policy information should be
preloaded (embedded in browsers).preload

Analysis

Good
Policy covers subdomains
When subdomains are included, network attackers are unable to manufacture arbitrary subdomains to manipulate cookies and trick users.
Good
Long policy age
Your HSTS policy has a long max-age value, which offers better protection.
Good
Policy is valid
OK. Your HSTS policy uses correct syntax.
Good
Redirection from HTTP to HTTPS to the same host
Good. The redirection from HTTP to HTTPS is to the same host. This approach ensures that HSTS is activated on the hostname when it's accessed via plaintext.
Good
Policy preloaded
Excellent. This host is covered by a preloaded HSTS policy.

Preloaded host: web.de; includeSubDomains=true

HSTS Policy  Apex host

URL from which this policy was obtained.Location https://web.de/
Specifies policy duration. Once activated, HSTS stays in force
until this time lapses. Browsers update policy cache duration
every time they receive a new HSTS header from a site.max‑age 		31,536,000 seconds (about 1 year)
When present, this directive forces HSTS activation
on allsubdomains. For best security, HSTS should be
deployed on the bare domain name (e.g., example.com)
and all its subdomains.includeSubDomains
Presence of this directive indicates that a web site wishes to
permanently use HSTS and that its policy information should be
preloaded (embedded in browsers).preload

Analysis

Good
Policy covers subdomains
When subdomains are included, network attackers are unable to manufacture arbitrary subdomains to manipulate cookies and trick users.
Good
Long policy age
Your HSTS policy has a long max-age value, which offers better protection.
Good
Policy is valid
OK. Your HSTS policy uses correct syntax.
Good
Redirection from HTTP to HTTPS to the same host
Good. The redirection from HTTP to HTTPS is to the same host. This approach ensures that HSTS is activated on the hostname when it's accessed via plaintext.
Good
Policy preloaded
Excellent. This host is covered by a preloaded HSTS policy.

Preloaded host: web.de; includeSubDomains=true

Good
Preload intent declared
Good. With the preload directive set, browsers have a green light to embed the HSTS policy.

HTTP Public Key Pinning

HTTP Public Key Pinning (HPKP) enables site operators to restrict which certificates are considered valid for their domain names. With a valid HPKP configuration, sites can defeat man in the middle (MITM) attacks using fraudulent or misissued certificates. HPKP is an advanced feature, suitable for use by only high-profile web sites.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Content Security Policy

Content Security Policy (CSP) is a security mechanism that allows web sites control how browsers process their pages. In essence, sites can restrict what types of resources are loaded and from where. CSP policies can be used to defend against cross-site scripting, prevent mixed content issues, as well as report violations for investigation.

Test passed
Everything seems to be well configured. Well done.

Content-Security-Policy

connect-src web.de   *.web.de   *.adition.com   *.mam.dev   *.netid.de   *.server.lan   *.ui-portal.de   *.uicdn.com   *.uimserv.net   united-infos.net   utiqcontent.com   *.adnami.io  
style-src This parameter shouldn't be used because it reenables
insecure behavior that CSP disables by default.'unsafe-inline'   web.de   *.web.de   *.ui-portal.de   *.uicdn.com  
script-src This parameter shouldn't be used because it reenables
insecure behavior that CSP disables by default.'unsafe-inline'   This parameter shouldn't be used because it reenables
insecure behavior that CSP disables by default.'unsafe-eval'   web.de   *.web.de   *.ui-portal.de   *.uicdn.com   *.uimserv.net   united-infos.net   *.adnami.io  
object-src 'none'
form-action web.de   *.web.de  
frame-src web.de   *.web.de   *.dpa-electionslive.com   *.dpa-sportslive.com   *.ergebnis-dienst.de   *.nativendo.de   *.ui-portal.de   *.uimserv.net   united-infos.net   *.adnami.io  
sandbox allow-forms   allow-popups   allow-popups-to-escape-sandbox   allow-same-origin   allow-scripts   allow-top-navigation-by-user-activation  
frame-ancestors 'self'   www.united-internet-media.de   adimg.uimserv.net   advideo.uimserv.net  
img-src data:   *  
default-src 'self'  
font-src data:   *.ui-portal.de  

Analysis

Powerup!
Inline styles are allowed
This policy allows inline styles. Although they are not as bad as inline scripts in terms of security, an injection bug in script area would allow the attacker to modify page appearance.
Powerup!
Inline scripts are allowed
By default, CSP doesn't allow inline script execution, but this policy overrides that behavior by specifying 'unsafe-inline' in the 'script-src' directive. As a result, all XSS defenses provided by CSP are significantly weakened.
Powerup!
Dynamic code execution is allowed
By default, CSP doesn't allow dynamic script execution via eval and friends, but this policy overrides that behavior by specifyin 'unsafe-eval' in the 'script-src' directive. As a result, XSS defenses provided by CSP are significantly weakened.
Powerup!
Mixed content not blocked
This CSP policy doesn't use any of the directives designed to handle mixed content. Consider using the 'block-all-mixed-content' and 'upgrade-insecure-requests' directives as appropriate to ensure that no mixed content is allowed.

Analysis

Info
CSP policy detected

Header: Content-Security-Policy

Value: connect-src web.de *.web.de *.adition.com *.mam.dev *.netid.de *.server.lan *.ui-portal.de *.uicdn.com *.uimserv.net united-infos.net utiqcontent.com *.adnami.io; style-src 'unsafe-inline' web.de *.web.de *.ui-portal.de *.uicdn.com *.web.de; script-src 'unsafe-inline' 'unsafe-eval' web.de *.web.de *.ui-portal.de *.uicdn.com *.uimserv.net united-infos.net *.adnami.io; object-src 'none'; form-action web.de *.web.de; frame-src web.de *.web.de *.dpa-electionslive.com *.dpa-sportslive.com *.ergebnis-dienst.de *.nativendo.de *.ui-portal.de *.uimserv.net united-infos.net *.adnami.io; sandbox allow-forms allow-popups allow-popups-to-escape-sandbox allow-same-origin allow-scripts allow-top-navigation-by-user-activation; frame-ancestors 'self' www.united-internet-media.de adimg.uimserv.net advideo.uimserv.net; img-src * data:; default-src 'self'; font-src data: *.ui-portal.de

Location: https://web.de/

Subresource Integrity

Subresource Integrity (SRI) is a new standard that enables browsers to verify the integrity of embedded page resources (e.g., scripts and stylesheets) when they are loaded from third-party web sites. With SRI deployed, remote resources can be used safely, without fear of them being modified by malicious parties.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.
6 script(s)
  4 out of 6 are secure
https://img.ui-portal.de/....7.3/tracklib.min.js
https://s.uicdn.com/...iq/mam/purple/daq.js
 View all
1 CSS file(s)
  0 out of 1 are secure
https://js.ui-portal.de/...bde/chunk-common.css
 View all

Analysis

Powerup!
SRI required
This page contains remote resources that are under the control of third parties. Deploy SRI to protect them from modification.

Expect CT

Expect-CT is a deprecated response HTTP header designed to enable web sites to monitor problems related to their Certificate Transparency (CT) compliance. Should any CT issues arise, browsers that supported this header will submit reports to the specified reporting endpoint. Chrome was the browser that introduced support for this response header, but later deprecated it and removed it in version 107.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Analysis

Powerup!
Deploy Expect-CT to enable reporting
An Expect-CT policy enables web sites to monitor for any problems related to their Expect-CT compliance, detecting potentially serious issues quickly. When issues arise, compliant browsers will submit reports to the specified reporting endpoints. Before CT became required for all public certificates the Expect-CT was also used to require CT, but that use case no longer applies.

Frame Options

The X-Frame-Options header controls page framing, which occurs when a page is incorporated into some other page, possibly on a different site. If framing is allowed, attackers can employ clever tricks to make victims perform arbitrary actions on your site; they do this by showing their web site while forwarding the victim's clicks to yours.

Test passed
Everything seems to be well configured. Well done.

Analysis

Info
Header information

Name: X-Frame-Options

Value: DENY

Good
Framing blocked
Good. Your site doesn't allow page framing from any other page.

XSS Protection

Some browsers ship with so-called XSS Auditors, built-in defenses against XSS. Although these defenses work against simple reflective XSS attacks, they can be abused by skillful attackers to add weaknesses to otherwise secure web sites. These dangers are present in both filtering and blocking modes. At this time, the Safari browser ships with its XSS defenses enabled by default. For this reason, the best approach is to explicitly disable this functionality.

Test passed
Everything seems to be well configured. Well done.

Analysis

Info
Header information

Name: X-Xss-Protection

Value: 0

Good
Browser XSS protection disabled
Great. XSS protection is explicitly disabled, making this web site safe even with browsers that have this functionality enabled by default.

Content Type Options

Some browsers use a technique called content sniffing to override response MIME types provided by HTTP servers and interpret responses as something else (usually HTML). This behavior, which could potentially lead to security issues, should be disabled by attaching an X-Content-Type-Options header to all responses.

Test passed
Everything seems to be well configured. Well done.

Analysis

Info
Header information

Name: X-Content-Type-Options

Value: nosniff

Good
Valid configuration
Good. Your configuration is valid. This means that browsers won't try to guess file MIME type on this web site.
Close Details