Check DNS, Urls + Redirects, Certificates and Content of your Website

0 in Queue, 1 of max. 8 Checks (17:13:19)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

A

 

Top config

 

Checked:
17.09.2019 16:34:41

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
mein.berlin.de
CNAME
mein-berlin-prod.liqd.net
yes
1
0

A
195.201.160.17
Falkenstein/Saxony/Germany (DE) - Hetzner
Hostname: hopper.liqd.net
yes



AAAA
2a01:4f8:13a:866::2
Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH

yes


www.mein.berlin.de
CNAME
mein-berlin-prod.liqd.net
yes
1
0

A
195.201.160.17
Falkenstein/Saxony/Germany (DE) - Hetzner
Hostname: hopper.liqd.net
yes



AAAA
2a01:4f8:13a:866::2
Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH

yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






• Status: Valid because published






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 59944, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 30.09.2019, 00:00:00 +, Signature-Inception: 09.09.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: de

de
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.09.2019, 05:00:00 +, Signature-Inception: 17.09.2019, 04:00:00 +, KeyTag 59944, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 59944 used to validate the DS RRSet in the parent zone






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 39227, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 43128, Flags 256






Public Key with Algorithm 8, KeyTag 44385, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 03.10.2019, 12:00:00 +, Signature-Inception: 12.09.2019, 12:00:00 +, KeyTag 39227, Signer-Name: de






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 39227 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 39227, DigestType 2 and Digest "qrcwg7nvcOSl6UdppBisEuiH/DwIde8gbDRR3EC2xPo=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: berlin.de

berlin.de
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "q5kgocqmvk1jb4g7sb0lmjgnkq33atb8" between the hashed NSEC3-owner "q5kdmp7p1l91bv5tbnopni8k2tm9h878" and the hashed NextOwner "q5kh3qangh0ho366d8ujiltet2j4cpuh". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner q5kdmp7p1l91bv5tbnopni8k2tm9h878.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 24.09.2019, 13:01:05 +, Signature-Inception: 17.09.2019, 13:01:05 +, KeyTag 44385, Signer-Name: de






0 DNSKEY RR found









Zone: mein.berlin.de

mein.berlin.de
0 DS RR in the parent zone found



Zone: www.mein.berlin.de

www.mein.berlin.de
0 DS RR in the parent zone found



Zone: (root)

(root)
1 DS RR published






• Status: Valid because published






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 59944, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 30.09.2019, 00:00:00 +, Signature-Inception: 09.09.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: net

net
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.09.2019, 05:00:00 +, Signature-Inception: 17.09.2019, 04:00:00 +, KeyTag 59944, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 59944 used to validate the DS RRSet in the parent zone






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 2129, Flags 256






Public Key with Algorithm 8, KeyTag 35886, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 59540, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.09.2019, 16:28:30 +, Signature-Inception: 07.09.2019, 16:23:30 +, KeyTag 35886, Signer-Name: net






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 35886 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 35886, DigestType 2 and Digest "eGKyf19Rbr4ZaARE1M5edimBkxhCxGXwAjZAHYvZc+4=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: liqd.net

liqd.net
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "kntc9dr942l7h44ulq3scc1q2og32d8c" between the hashed NSEC3-owner "kntbdf9a72so45tjop0b2i5lfsc67shf" and the hashed NextOwner "kntjp7ea8t873lr1v98dq748u2a8m7fq". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner kntbdf9a72so45tjop0b2i5lfsc67shf.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 24.09.2019, 05:55:55 +, Signature-Inception: 17.09.2019, 04:45:55 +, KeyTag 59540, Signer-Name: net






0 DNSKEY RR found









Zone: mein-berlin-prod.liqd.net

mein-berlin-prod.liqd.net
0 DS RR in the parent zone found






0 DNSKEY RR found







 

3. Name Servers

DomainNameserverNS-IP
berlin.de
•  ns-1460.awsdns-54.org / 4b65f8097a21711bd312c3a7a90557c5 -
•

•  ns-1719.awsdns-22.co.uk / 34c51919bfdc542a899dad433ea6fa5c -
•

•  ns-391.awsdns-48.com / b2011fb97fe0b7a76269055489f99c01 -
•

•  ns-931.awsdns-52.net / a50c7c46d74217c10ed26284a8fbf9f5 -
•
de
•  a.nic.de / ns-2.de.de8.bind
•

•  f.nic.de / ns-1.de.de1.bind
•

•  l.de.net / ns-1.de.fr1.bind
•

•  n.de.net / s3.amx
•

•  s.de.net / ns-2.de.de9.bind
•

•  z.nic.de / ns-2.de.de8.bind
•
mein-berlin-prod.liqd.net
•  ns1.first-ns.de
213.239.242.238
Frankfurt am Main/Hesse/Germany (DE) - Hetzner Online GmbH		•

• 
2a01:4f8:0:a101::a:1
Frankfurt am Main/Hesse/Germany (DE) - Hetzner Online GmbH		•
liqd.net
•  ns1.first-ns.de
•

•  robotns2.second-ns.de
•

•  robotns3.second-ns.com
•
net
•  a.gtld-servers.net
•

•  b.gtld-servers.net
•

•  c.gtld-servers.net
•

•  d.gtld-servers.net
•

•  e.gtld-servers.net
•

•  f.gtld-servers.net
•

•  g.gtld-servers.net
•

•  h.gtld-servers.net
•

•  i.gtld-servers.net
•

•  j.gtld-servers.net
•

•  k.gtld-servers.net
•

•  l.gtld-servers.net
•

•  m.gtld-servers.net
•

 

4. SOA-Entries


Domain:de
Zone-Name:
Primary:f.nic.de
Mail:its.denic.de
Serial:2019091765
Refresh:7200
Retry:7200
Expire:3600000
TTL:7200
num Entries:6


Domain:berlin.de
Zone-Name:
Primary:ns-931.awsdns-52.net
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:4


Domain:net
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1568730869
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:11


Domain:net
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1568730884
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:2


Domain:liqd.net
Zone-Name:
Primary:ns1.first-ns.de
Mail:postmaster.robot.first-ns.de
Serial:2019042401
Refresh:14400
Retry:1800
Expire:604800
TTL:86400
num Entries:3


Domain:mein-berlin-prod.liqd.net
Zone-Name:
Primary:ns1.first-ns.de
Mail:postmaster.robot.first-ns.de
Serial:2019042401
Refresh:14400
Retry:1800
Expire:604800
TTL:86400
num Entries:2


5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://mein.berlin.de/
195.201.160.17
301
https://mein.berlin.de/
Html is minified: 107.78 %
0.046
A
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 17 Sep 2019 14:35:50 GMT
Content-Type: text/html
Content-Length: 194
Connection: close
Location: https://mein.berlin.de/

• http://mein.berlin.de/
2a01:4f8:13a:866::2
301
https://mein.berlin.de/
Html is minified: 107.78 %
0.047
A
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 17 Sep 2019 14:35:50 GMT
Content-Type: text/html
Content-Length: 194
Connection: close
Location: https://mein.berlin.de/

• http://www.mein.berlin.de/
195.201.160.17
301
https://www.mein.berlin.de/
Html is minified: 107.78 %
0.050
A
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 17 Sep 2019 14:35:50 GMT
Content-Type: text/html
Content-Length: 194
Connection: close
Location: https://www.mein.berlin.de/

• http://www.mein.berlin.de/
2a01:4f8:13a:866::2
301
https://www.mein.berlin.de/
Html is minified: 107.78 %
0.053
A
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 17 Sep 2019 14:35:50 GMT
Content-Type: text/html
Content-Length: 194
Connection: close
Location: https://www.mein.berlin.de/

• https://www.mein.berlin.de/
195.201.160.17
301
https://mein.berlin.de/
Html is minified: 107.78 %
3.193
A
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 17 Sep 2019 14:36:00 GMT
Content-Type: text/html
Content-Length: 194
Connection: close
Location: https://mein.berlin.de/
Strict-Transport-Security: max-age=15552000; includeSubdomains; preload
Expect-CT: max-age=15552000, enforce

• https://www.mein.berlin.de/
2a01:4f8:13a:866::2
301
https://mein.berlin.de/
Html is minified: 107.78 %
3.144
A
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 17 Sep 2019 14:36:03 GMT
Content-Type: text/html
Content-Length: 194
Connection: close
Location: https://mein.berlin.de/
Strict-Transport-Security: max-age=15552000; includeSubdomains; preload
Expect-CT: max-age=15552000, enforce

• https://mein.berlin.de/
195.201.160.17
Inline-JavaScript (∑/total): 1/525 Inline-CSS (∑/total): 0/0		200

Html is minified: 137.23 %
Other inline scripts (∑/total): 1/525		4.486
A
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 17 Sep 2019 14:35:52 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding,Accept-Encoding,Cookie
x-ajax-path: /
Link: </static/adhocracy4.e37d662789cf.css>; rel=preload; as=style, </static/vendor.f34320aa76fe.css>; rel=preload; as=style, </static/vendor.0ab2676d5368.js>; rel=preload; as=script, </static/adhocracy4.1613cc7514cd.js>; rel=preload; as=script, </static/images/icon_infografik_arrow_down@2x.49768df2e192.png>; rel=preload; as=image, </static/images/LOGO.3b6ad04942c9.png>; rel=preload; as=image, </static/images/icon_infografik_arrow_up@2x.952fcb705129.png>; rel=preload; as=image, </static/images/berlin_de.f4e51682c35a.png>; rel=preload; as=image, </static/images/icon_infografik_folgen.a280631d9970.png>; rel=preload; as=image, </static/images/icon_infografik_projekte.f02099fb64a3.png>; rel=preload; as=image,</jsi18n/>; as=script; rel=preload
Content-Security-Policy: script-src 'self' 'unsafe-inline' blob: https://stats.liqd.net; upgrade-insecure-requests; block-all-mixed-content; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://meinberlin-media.liqd.net *.tile.openstreetmap.org https://*.berlinonline.de https://stats.liqd.net; connect-src 'self' https://bplan-prod.liqd.net https://*.berlinonline.de; default-src 'self' https://stats.liqd.net; child-src blob:
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Strict-Transport-Security: max-age=15552000; includeSubdomains; preload
Expect-CT: max-age=15552000, enforce
Content-Encoding: gzip

• https://mein.berlin.de/
2a01:4f8:13a:866::2
Inline-JavaScript (∑/total): 1/525 Inline-CSS (∑/total): 0/0		200

Html is minified: 138.03 %
Other inline scripts (∑/total): 1/525		4.196
A
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 17 Sep 2019 14:35:56 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding,Accept-Encoding,Cookie
x-ajax-path: /
Link: </static/adhocracy4.e37d662789cf.css>; rel=preload; as=style, </static/vendor.f34320aa76fe.css>; rel=preload; as=style, </static/vendor.0ab2676d5368.js>; rel=preload; as=script, </static/adhocracy4.1613cc7514cd.js>; rel=preload; as=script, </static/images/icon_infografik_arrow_down@2x.49768df2e192.png>; rel=preload; as=image, </static/images/LOGO.3b6ad04942c9.png>; rel=preload; as=image, </static/images/icon_infografik_arrow_up@2x.952fcb705129.png>; rel=preload; as=image, </static/images/berlin_de.f4e51682c35a.png>; rel=preload; as=image, </static/images/icon_infografik_folgen.a280631d9970.png>; rel=preload; as=image, </static/images/icon_infografik_projekte.f02099fb64a3.png>; rel=preload; as=image,</jsi18n/>; as=script; rel=preload
Content-Security-Policy: script-src 'self' 'unsafe-inline' blob: https://stats.liqd.net; upgrade-insecure-requests; block-all-mixed-content; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://meinberlin-media.liqd.net *.tile.openstreetmap.org https://*.berlinonline.de https://stats.liqd.net; connect-src 'self' https://bplan-prod.liqd.net https://*.berlinonline.de; default-src 'self' https://stats.liqd.net; child-src blob:
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Strict-Transport-Security: max-age=15552000; includeSubdomains; preload
Expect-CT: max-age=15552000, enforce
Content-Encoding: gzip

• http://mein.berlin.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
195.201.160.17
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 108.54 %
Other inline scripts (∑/total): 0/0		0.050
A
Not Found
Visible Content: 404 Not Found nginx/1.14.0 (Ubuntu)
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 17 Sep 2019 14:36:06 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Content-Encoding: gzip

• http://mein.berlin.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a01:4f8:13a:866::2
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 108.54 %
Other inline scripts (∑/total): 0/0		0.047
A
Not Found
Visible Content: 404 Not Found nginx/1.14.0 (Ubuntu)
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 17 Sep 2019 14:36:06 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Content-Encoding: gzip

• http://www.mein.berlin.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
195.201.160.17
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 108.54 %
Other inline scripts (∑/total): 0/0		0.050
A
Not Found
Visible Content: 404 Not Found nginx/1.14.0 (Ubuntu)
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 17 Sep 2019 14:36:07 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Content-Encoding: gzip

• http://www.mein.berlin.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a01:4f8:13a:866::2
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 108.54 %
Other inline scripts (∑/total): 0/0		0.050
A
Not Found
Visible Content: 404 Not Found nginx/1.14.0 (Ubuntu)
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 17 Sep 2019 14:36:07 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Content-Encoding: gzip

 

7. Comments


1. General Results, most used to calculate the result

Aname "mein.berlin.de" is subdomain, public suffix is "de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: every https has a Strict Transport Security Header
AGood: HSTS has includeSubdomains - directive
AGood: HSTS has preload directive
Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (6 urls)
http://mein.berlin.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 195.201.160.17


Url with incomplete Content-Type - header - missing charset
http://mein.berlin.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:13a:866::2


Url with incomplete Content-Type - header - missing charset
http://www.mein.berlin.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 195.201.160.17


Url with incomplete Content-Type - header - missing charset
http://www.mein.berlin.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:13a:866::2


Url with incomplete Content-Type - header - missing charset
Ahttp://mein.berlin.de/ 195.201.160.17
301
https://mein.berlin.de/
Correct redirect http - https with the same domain name
Ahttp://mein.berlin.de/ 2a01:4f8:13a:866::2
301
https://mein.berlin.de/
Correct redirect http - https with the same domain name
Ahttp://www.mein.berlin.de/ 195.201.160.17
301
https://www.mein.berlin.de/
Correct redirect http - https with the same domain name
Ahttp://www.mein.berlin.de/ 2a01:4f8:13a:866::2
301
https://www.mein.berlin.de/
Correct redirect http - https with the same domain name
BWarning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15552000 seconds = 180 days found

2. Header-Checks


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
AGood: All SOA have the same Serial Number
AGood: CAA entries found, creating certificate is limited: comodoca.com is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: globalsign.com is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: telesec.de is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: no CAA is allowed to create wildcard certificates

4. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 106960 milliseconds, 106.960 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
mein.berlin.de
195.201.160.17
443
ok
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
supported
ok
mein.berlin.de
195.201.160.17
443
ok
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
supported
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=mein.berlin.de


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


mein.berlin.de
2a01:4f8:13a:866::2
443
ok
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
supported
ok

mein.berlin.de
2a01:4f8:13a:866::2
443
ok
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
supported
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=mein.berlin.de


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


www.mein.berlin.de
195.201.160.17
443
ok
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
supported
ok

www.mein.berlin.de
195.201.160.17
443
ok
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
supported
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=mein.berlin.de


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


www.mein.berlin.de
2a01:4f8:13a:866::2
443
ok
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
supported
ok

www.mein.berlin.de
2a01:4f8:13a:866::2
443
ok
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
supported
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=mein.berlin.de


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

 

9. Certificates

1.
1.
CN=mein.berlin.de
16.09.2019
15.12.2019
1980 days expired		mein.berlin.de, www.mein.berlin.de - 2 entries
1.
1.
CN=mein.berlin.de
16.09.2019

15.12.2019
1980 days expired


mein.berlin.de, www.mein.berlin.de - 2 entries

KeyalgorithmEC Public Key (256 bit, prime256v1)
Signatur:SHA256 With RSA-Encryption
Serial Number:031134B60159DEC4D7364C0A9DB2FD55EBD8
Thumbprint:8FA6D9C324C34824030887C80216FB213B0A8463
SHA256 / Certificate:w81IcjkxtyDgmqYaPDH4k1YKgUtfiIg4BRv9m8t6HJM=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):a55f1c429df512e37b37c85abfde60f7342a3eb3fd84a0c3300265d8cf2a01e4
SHA256 hex / Subject Public Key Information (SPKI):a55f1c429df512e37b37c85abfde60f7342a3eb3fd84a0c3300265d8cf2a01e4
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)




2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
1522 days expired

2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
1522 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
1325 days expired

3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
1325 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




 

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0
0
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
6994469267
leaf cert		CN=R3, O=Let's Encrypt, C=US
2024-03-24 10:00:24
2024-06-22 10:00:23
mein.berlin.de, www.mein.berlin.de - 2 entries


6994466322
leaf cert		CN=R3, O=Let's Encrypt, C=US
2024-03-24 10:00:16
2024-06-22 10:00:15
mein.berlin.de, www.mein.berlin.de - 2 entries


 

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

No CRT - CT-Log entries found

 

11. Html-Content - Entries

Summary

No data found or small Code-update

 

Details (currently limited to 500 rows - some problems with spam users)

Small Code Update - wait one minute

 

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

 

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
mein-berlin-prod.liqd.net
5
issue
globalsign.com
1
0

5
issue
letsencrypt.org
1
0

5
iodef
mailto:webmaster@liqd.net
1
0
www.mein.berlin.de



1
0
mein.berlin.de



1
0
berlin.de
9
issuewild
;
1
0

5
issue
comodoca.com
1
0

5
issue
digicert.com
1
0

5
issue
globalsign.com
1
0

5
issue
letsencrypt.org
1
0

32773
iodef
mailto:webmaster@berlinonline.net
1
0

5
issue
telesec.de
1
0
liqd.net
5
issue
globalsign.com
1
0

5
issue
letsencrypt.org
1
0

5
iodef
mailto:webmaster@liqd.net
1
0
net
0

no CAA entry found
1
0
de
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
liqd.net
v=spf1 mx include:mailbox.org include:jpberlin.de a:hopper.liqd.net a:conway.liqd.net ip4:80.82.200.225 ip6:2a00:cd0:104e:442:10:12:164:201 ~all
ok
1
0
berlin.de
v=spf1 mx ip4:212.45.105.224/28 ip4:212.45.111.16/30 ip4:144.76.202.176 ip6:2a00:cd0:1002:320::/64 a:mailout1.berlinonline.net. a:service.berlinonline.de ip4:144.76.248.115 include:amazonses.com include:_spf.ops.eusc.inter.net ~all
ok
1
0
mein.berlin.de


1
0
www.mein.berlin.de


1
0
mein-berlin-prod.liqd.net
v=spf1 include:liqd.net ~all
ok
1
0
_acme-challenge.mein.berlin.de

Name Error - The domain name does not exist
1
0
_acme-challenge.www.mein.berlin.de

Name Error - The domain name does not exist
1
0
_acme-challenge.mein.berlin.de.berlin.de

Name Error - The domain name does not exist
1
0
_acme-challenge.mein-berlin-prod.liqd.net

Name Error - The domain name does not exist
1
0
_acme-challenge.mein.berlin.de.mein.berlin.de

Name Error - The domain name does not exist
1
0
_acme-challenge.www.mein.berlin.de.mein.berlin.de

Name Error - The domain name does not exist
1
0
_acme-challenge.mein-berlin-prod.liqd.net.liqd.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.mein.berlin.de.www.mein.berlin.de

Name Error - The domain name does not exist
1
0
_acme-challenge.mein-berlin-prod.liqd.net.mein-berlin-prod.liqd.net

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

DomainIPPortDescriptionResultAnswer
mein.berlin.de
195.201.160.17
21
FTP



mein.berlin.de
195.201.160.17
21
FTP



www.mein.berlin.de
195.201.160.17
21
FTP



www.mein.berlin.de
195.201.160.17
21
FTP



www.mein.berlin.de
195.201.160.17
22
SSH



www.mein.berlin.de
195.201.160.17
22
SSH



mein.berlin.de
195.201.160.17
22
SSH



mein.berlin.de
195.201.160.17
22
SSH



mein.berlin.de
195.201.160.17
25
SMTP



mein.berlin.de
195.201.160.17
25
SMTP



www.mein.berlin.de
195.201.160.17
25
SMTP



www.mein.berlin.de
195.201.160.17
25
SMTP



mein.berlin.de
195.201.160.17
53
DNS



mein.berlin.de
195.201.160.17
53
DNS



www.mein.berlin.de
195.201.160.17
53
DNS



www.mein.berlin.de
195.201.160.17
53
DNS



mein.berlin.de
195.201.160.17
110
POP3



mein.berlin.de
195.201.160.17
110
POP3



www.mein.berlin.de
195.201.160.17
110
POP3



www.mein.berlin.de
195.201.160.17
110
POP3



www.mein.berlin.de
195.201.160.17
143
IMAP



www.mein.berlin.de
195.201.160.17
143
IMAP



mein.berlin.de
195.201.160.17
143
IMAP



mein.berlin.de
195.201.160.17
143
IMAP



mein.berlin.de
195.201.160.17
465
SMTP (encrypted)



mein.berlin.de
195.201.160.17
465
SMTP (encrypted)



www.mein.berlin.de
195.201.160.17
465
SMTP (encrypted)



www.mein.berlin.de
195.201.160.17
465
SMTP (encrypted)



www.mein.berlin.de
195.201.160.17
587
SMTP (encrypted, submission)



www.mein.berlin.de
195.201.160.17
587
SMTP (encrypted, submission)



mein.berlin.de
195.201.160.17
587
SMTP (encrypted, submission)



mein.berlin.de
195.201.160.17
587
SMTP (encrypted, submission)



mein.berlin.de
195.201.160.17
993
IMAP (encrypted)



mein.berlin.de
195.201.160.17
993
IMAP (encrypted)



www.mein.berlin.de
195.201.160.17
993
IMAP (encrypted)



www.mein.berlin.de
195.201.160.17
993
IMAP (encrypted)



www.mein.berlin.de
195.201.160.17
995
POP3 (encrypted)



www.mein.berlin.de
195.201.160.17
995
POP3 (encrypted)



mein.berlin.de
195.201.160.17
995
POP3 (encrypted)



mein.berlin.de
195.201.160.17
995
POP3 (encrypted)



mein.berlin.de
195.201.160.17
1433
MS SQL



mein.berlin.de
195.201.160.17
1433
MS SQL



www.mein.berlin.de
195.201.160.17
1433
MS SQL



www.mein.berlin.de
195.201.160.17
1433
MS SQL



www.mein.berlin.de
195.201.160.17
2082
cPanel (http)



www.mein.berlin.de
195.201.160.17
2082
cPanel (http)



mein.berlin.de
195.201.160.17
2082
cPanel (http)



mein.berlin.de
195.201.160.17
2082
cPanel (http)



mein.berlin.de
195.201.160.17
2083
cPanel (https)



mein.berlin.de
195.201.160.17
2083
cPanel (https)



www.mein.berlin.de
195.201.160.17
2083
cPanel (https)



www.mein.berlin.de
195.201.160.17
2083
cPanel (https)



mein.berlin.de
195.201.160.17
2086
WHM (http)



mein.berlin.de
195.201.160.17
2086
WHM (http)



www.mein.berlin.de
195.201.160.17
2086
WHM (http)



www.mein.berlin.de
195.201.160.17
2086
WHM (http)



mein.berlin.de
195.201.160.17
2087
WHM (https)



mein.berlin.de
195.201.160.17
2087
WHM (https)



www.mein.berlin.de
195.201.160.17
2087
WHM (https)



www.mein.berlin.de
195.201.160.17
2087
WHM (https)



mein.berlin.de
195.201.160.17
2089
cPanel Licensing



mein.berlin.de
195.201.160.17
2089
cPanel Licensing



www.mein.berlin.de
195.201.160.17
2089
cPanel Licensing



www.mein.berlin.de
195.201.160.17
2089
cPanel Licensing



www.mein.berlin.de
195.201.160.17
2095
cPanel Webmail (http)



www.mein.berlin.de
195.201.160.17
2095
cPanel Webmail (http)



mein.berlin.de
195.201.160.17
2095
cPanel Webmail (http)



mein.berlin.de
195.201.160.17
2095
cPanel Webmail (http)



mein.berlin.de
195.201.160.17
2096
cPanel Webmail (https)



mein.berlin.de
195.201.160.17
2096
cPanel Webmail (https)



www.mein.berlin.de
195.201.160.17
2096
cPanel Webmail (https)



www.mein.berlin.de
195.201.160.17
2096
cPanel Webmail (https)



www.mein.berlin.de
195.201.160.17
2222
DirectAdmin (http)



www.mein.berlin.de
195.201.160.17
2222
DirectAdmin (http)



www.mein.berlin.de
195.201.160.17
2222
DirectAdmin (https)



www.mein.berlin.de
195.201.160.17
2222
DirectAdmin (https)



mein.berlin.de
195.201.160.17
2222
DirectAdmin (http)



mein.berlin.de
195.201.160.17
2222
DirectAdmin (http)



mein.berlin.de
195.201.160.17
2222
DirectAdmin (https)



mein.berlin.de
195.201.160.17
2222
DirectAdmin (https)



mein.berlin.de
195.201.160.17
3306
mySql



mein.berlin.de
195.201.160.17
3306
mySql



www.mein.berlin.de
195.201.160.17
3306
mySql



www.mein.berlin.de
195.201.160.17
3306
mySql



www.mein.berlin.de
195.201.160.17
5224
Plesk Licensing



www.mein.berlin.de
195.201.160.17
5224
Plesk Licensing



mein.berlin.de
195.201.160.17
5224
Plesk Licensing



mein.berlin.de
195.201.160.17
5224
Plesk Licensing



mein.berlin.de
195.201.160.17
5432
PostgreSQL



mein.berlin.de
195.201.160.17
5432
PostgreSQL



www.mein.berlin.de
195.201.160.17
5432
PostgreSQL



www.mein.berlin.de
195.201.160.17
5432
PostgreSQL



www.mein.berlin.de
195.201.160.17
8080
Ookla Speedtest (http)



www.mein.berlin.de
195.201.160.17
8080
Ookla Speedtest (http)



www.mein.berlin.de
195.201.160.17
8080
Ookla Speedtest (https)



www.mein.berlin.de
195.201.160.17
8080
Ookla Speedtest (https)



mein.berlin.de
195.201.160.17
8080
Ookla Speedtest (http)



mein.berlin.de
195.201.160.17
8080
Ookla Speedtest (http)



mein.berlin.de
195.201.160.17
8080
Ookla Speedtest (https)



mein.berlin.de
195.201.160.17
8080
Ookla Speedtest (https)



mein.berlin.de
195.201.160.17
8083
VestaCP http



mein.berlin.de
195.201.160.17
8083
VestaCP http



mein.berlin.de
195.201.160.17
8083
VestaCP https



mein.berlin.de
195.201.160.17
8083
VestaCP https



www.mein.berlin.de
195.201.160.17
8083
VestaCP http



www.mein.berlin.de
195.201.160.17
8083
VestaCP http



www.mein.berlin.de
195.201.160.17
8083
VestaCP https



www.mein.berlin.de
195.201.160.17
8083
VestaCP https



mein.berlin.de
195.201.160.17
8443
Plesk Administration (https)



mein.berlin.de
195.201.160.17
8443
Plesk Administration (https)



www.mein.berlin.de
195.201.160.17
8443
Plesk Administration (https)



www.mein.berlin.de
195.201.160.17
8443
Plesk Administration (https)



www.mein.berlin.de
195.201.160.17
8447
Plesk Installer + Updates



www.mein.berlin.de
195.201.160.17
8447
Plesk Installer + Updates



mein.berlin.de
195.201.160.17
8447
Plesk Installer + Updates



mein.berlin.de
195.201.160.17
8447
Plesk Installer + Updates



mein.berlin.de
195.201.160.17
8880
Plesk Administration (http)



mein.berlin.de
195.201.160.17
8880
Plesk Administration (http)



www.mein.berlin.de
195.201.160.17
8880
Plesk Administration (http)



www.mein.berlin.de
195.201.160.17
8880
Plesk Administration (http)



mein.berlin.de
195.201.160.17
10000
Webmin (http)



mein.berlin.de
195.201.160.17
10000
Webmin (http)



mein.berlin.de
195.201.160.17
10000
Webmin (https)



mein.berlin.de
195.201.160.17
10000
Webmin (https)



www.mein.berlin.de
195.201.160.17
10000
Webmin (http)



www.mein.berlin.de
195.201.160.17
10000
Webmin (http)



www.mein.berlin.de
195.201.160.17
10000
Webmin (https)



www.mein.berlin.de
195.201.160.17
10000
Webmin (https)



www.mein.berlin.de
2a01:4f8:13a:866::2
21
FTP



www.mein.berlin.de
2a01:4f8:13a:866::2
21
FTP



mein.berlin.de
2a01:4f8:13a:866::2
21
FTP



mein.berlin.de
2a01:4f8:13a:866::2
21
FTP



mein.berlin.de
2a01:4f8:13a:866::2
22
SSH



mein.berlin.de
2a01:4f8:13a:866::2
22
SSH



www.mein.berlin.de
2a01:4f8:13a:866::2
22
SSH



www.mein.berlin.de
2a01:4f8:13a:866::2
22
SSH



www.mein.berlin.de
2a01:4f8:13a:866::2
25
SMTP



www.mein.berlin.de
2a01:4f8:13a:866::2
25
SMTP



mein.berlin.de
2a01:4f8:13a:866::2
25
SMTP



mein.berlin.de
2a01:4f8:13a:866::2
25
SMTP



mein.berlin.de
2a01:4f8:13a:866::2
53
DNS



mein.berlin.de
2a01:4f8:13a:866::2
53
DNS



www.mein.berlin.de
2a01:4f8:13a:866::2
53
DNS



www.mein.berlin.de
2a01:4f8:13a:866::2
53
DNS



www.mein.berlin.de
2a01:4f8:13a:866::2
110
POP3



www.mein.berlin.de
2a01:4f8:13a:866::2
110
POP3



mein.berlin.de
2a01:4f8:13a:866::2
110
POP3



mein.berlin.de
2a01:4f8:13a:866::2
110
POP3



mein.berlin.de
2a01:4f8:13a:866::2
143
IMAP



mein.berlin.de
2a01:4f8:13a:866::2
143
IMAP



www.mein.berlin.de
2a01:4f8:13a:866::2
143
IMAP



www.mein.berlin.de
2a01:4f8:13a:866::2
143
IMAP



www.mein.berlin.de
2a01:4f8:13a:866::2
465
SMTP (encrypted)



www.mein.berlin.de
2a01:4f8:13a:866::2
465
SMTP (encrypted)



mein.berlin.de
2a01:4f8:13a:866::2
465
SMTP (encrypted)



mein.berlin.de
2a01:4f8:13a:866::2
465
SMTP (encrypted)



mein.berlin.de
2a01:4f8:13a:866::2
587
SMTP (encrypted, submission)



mein.berlin.de
2a01:4f8:13a:866::2
587
SMTP (encrypted, submission)



www.mein.berlin.de
2a01:4f8:13a:866::2
587
SMTP (encrypted, submission)



www.mein.berlin.de
2a01:4f8:13a:866::2
587
SMTP (encrypted, submission)



www.mein.berlin.de
2a01:4f8:13a:866::2
993
IMAP (encrypted)



www.mein.berlin.de
2a01:4f8:13a:866::2
993
IMAP (encrypted)



mein.berlin.de
2a01:4f8:13a:866::2
993
IMAP (encrypted)



mein.berlin.de
2a01:4f8:13a:866::2
993
IMAP (encrypted)



mein.berlin.de
2a01:4f8:13a:866::2
995
POP3 (encrypted)



mein.berlin.de
2a01:4f8:13a:866::2
995
POP3 (encrypted)



www.mein.berlin.de
2a01:4f8:13a:866::2
995
POP3 (encrypted)



www.mein.berlin.de
2a01:4f8:13a:866::2
995
POP3 (encrypted)



www.mein.berlin.de
2a01:4f8:13a:866::2
1433
MS SQL



www.mein.berlin.de
2a01:4f8:13a:866::2
1433
MS SQL



mein.berlin.de
2a01:4f8:13a:866::2
1433
MS SQL



mein.berlin.de
2a01:4f8:13a:866::2
1433
MS SQL



mein.berlin.de
2a01:4f8:13a:866::2
2082
cPanel (http)



mein.berlin.de
2a01:4f8:13a:866::2
2082
cPanel (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
2082
cPanel (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
2082
cPanel (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
2083
cPanel (https)



www.mein.berlin.de
2a01:4f8:13a:866::2
2083
cPanel (https)



mein.berlin.de
2a01:4f8:13a:866::2
2083
cPanel (https)



mein.berlin.de
2a01:4f8:13a:866::2
2083
cPanel (https)



mein.berlin.de
2a01:4f8:13a:866::2
2086
WHM (http)



mein.berlin.de
2a01:4f8:13a:866::2
2086
WHM (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
2086
WHM (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
2086
WHM (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
2087
WHM (https)



www.mein.berlin.de
2a01:4f8:13a:866::2
2087
WHM (https)



mein.berlin.de
2a01:4f8:13a:866::2
2087
WHM (https)



mein.berlin.de
2a01:4f8:13a:866::2
2087
WHM (https)



mein.berlin.de
2a01:4f8:13a:866::2
2089
cPanel Licensing



mein.berlin.de
2a01:4f8:13a:866::2
2089
cPanel Licensing



www.mein.berlin.de
2a01:4f8:13a:866::2
2089
cPanel Licensing



www.mein.berlin.de
2a01:4f8:13a:866::2
2089
cPanel Licensing



www.mein.berlin.de
2a01:4f8:13a:866::2
2095
cPanel Webmail (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
2095
cPanel Webmail (http)



mein.berlin.de
2a01:4f8:13a:866::2
2095
cPanel Webmail (http)



mein.berlin.de
2a01:4f8:13a:866::2
2095
cPanel Webmail (http)



mein.berlin.de
2a01:4f8:13a:866::2
2096
cPanel Webmail (https)



mein.berlin.de
2a01:4f8:13a:866::2
2096
cPanel Webmail (https)



www.mein.berlin.de
2a01:4f8:13a:866::2
2096
cPanel Webmail (https)



www.mein.berlin.de
2a01:4f8:13a:866::2
2096
cPanel Webmail (https)



www.mein.berlin.de
2a01:4f8:13a:866::2
2222
DirectAdmin (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
2222
DirectAdmin (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
2222
DirectAdmin (https)



www.mein.berlin.de
2a01:4f8:13a:866::2
2222
DirectAdmin (https)



mein.berlin.de
2a01:4f8:13a:866::2
2222
DirectAdmin (http)



mein.berlin.de
2a01:4f8:13a:866::2
2222
DirectAdmin (http)



mein.berlin.de
2a01:4f8:13a:866::2
2222
DirectAdmin (https)



mein.berlin.de
2a01:4f8:13a:866::2
2222
DirectAdmin (https)



mein.berlin.de
2a01:4f8:13a:866::2
3306
mySql



mein.berlin.de
2a01:4f8:13a:866::2
3306
mySql



www.mein.berlin.de
2a01:4f8:13a:866::2
3306
mySql



www.mein.berlin.de
2a01:4f8:13a:866::2
3306
mySql



www.mein.berlin.de
2a01:4f8:13a:866::2
5224
Plesk Licensing



www.mein.berlin.de
2a01:4f8:13a:866::2
5224
Plesk Licensing



mein.berlin.de
2a01:4f8:13a:866::2
5224
Plesk Licensing



mein.berlin.de
2a01:4f8:13a:866::2
5224
Plesk Licensing



mein.berlin.de
2a01:4f8:13a:866::2
5432
PostgreSQL



mein.berlin.de
2a01:4f8:13a:866::2
5432
PostgreSQL



www.mein.berlin.de
2a01:4f8:13a:866::2
5432
PostgreSQL



www.mein.berlin.de
2a01:4f8:13a:866::2
5432
PostgreSQL



www.mein.berlin.de
2a01:4f8:13a:866::2
8080
Ookla Speedtest (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
8080
Ookla Speedtest (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
8080
Ookla Speedtest (https)



www.mein.berlin.de
2a01:4f8:13a:866::2
8080
Ookla Speedtest (https)



mein.berlin.de
2a01:4f8:13a:866::2
8080
Ookla Speedtest (http)



mein.berlin.de
2a01:4f8:13a:866::2
8080
Ookla Speedtest (http)



mein.berlin.de
2a01:4f8:13a:866::2
8080
Ookla Speedtest (https)



mein.berlin.de
2a01:4f8:13a:866::2
8080
Ookla Speedtest (https)



mein.berlin.de
2a01:4f8:13a:866::2
8083
VestaCP http



mein.berlin.de
2a01:4f8:13a:866::2
8083
VestaCP http



mein.berlin.de
2a01:4f8:13a:866::2
8083
VestaCP https



mein.berlin.de
2a01:4f8:13a:866::2
8083
VestaCP https



www.mein.berlin.de
2a01:4f8:13a:866::2
8083
VestaCP http



www.mein.berlin.de
2a01:4f8:13a:866::2
8083
VestaCP http



www.mein.berlin.de
2a01:4f8:13a:866::2
8083
VestaCP https



www.mein.berlin.de
2a01:4f8:13a:866::2
8083
VestaCP https



www.mein.berlin.de
2a01:4f8:13a:866::2
8443
Plesk Administration (https)



www.mein.berlin.de
2a01:4f8:13a:866::2
8443
Plesk Administration (https)



mein.berlin.de
2a01:4f8:13a:866::2
8443
Plesk Administration (https)



mein.berlin.de
2a01:4f8:13a:866::2
8443
Plesk Administration (https)



mein.berlin.de
2a01:4f8:13a:866::2
8447
Plesk Installer + Updates



mein.berlin.de
2a01:4f8:13a:866::2
8447
Plesk Installer + Updates



www.mein.berlin.de
2a01:4f8:13a:866::2
8447
Plesk Installer + Updates



www.mein.berlin.de
2a01:4f8:13a:866::2
8447
Plesk Installer + Updates



www.mein.berlin.de
2a01:4f8:13a:866::2
8880
Plesk Administration (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
8880
Plesk Administration (http)



mein.berlin.de
2a01:4f8:13a:866::2
8880
Plesk Administration (http)



mein.berlin.de
2a01:4f8:13a:866::2
8880
Plesk Administration (http)



mein.berlin.de
2a01:4f8:13a:866::2
10000
Webmin (http)



mein.berlin.de
2a01:4f8:13a:866::2
10000
Webmin (http)



mein.berlin.de
2a01:4f8:13a:866::2
10000
Webmin (https)



mein.berlin.de
2a01:4f8:13a:866::2
10000
Webmin (https)



www.mein.berlin.de
2a01:4f8:13a:866::2
10000
Webmin (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
10000
Webmin (http)



www.mein.berlin.de
2a01:4f8:13a:866::2
10000
Webmin (https)



www.mein.berlin.de
2a01:4f8:13a:866::2
10000
Webmin (https)



 

 

Permalink: https://check-your-website.server-daten.de/?i=692c5a97-0c79-4f4e-acb5-d61770d4a20f

 

Last Result: https://check-your-website.server-daten.de/?q=mein.berlin.de - 2019-09-17 16:34:41

 

Do you like this page? Support this tool, add a link on your page:

 

<a href="https://check-your-website.server-daten.de/?q=mein.berlin.de" target="_blank">Check this Site: mein.berlin.de</a>

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=mein.berlin.de

 

 

Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

 

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions