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

0 in Queue, 0 of max. 8 Checks (18:19:38)
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 configuration, no warnings +Preload

 

Checked:
28.09.2023 18:51:01

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
cloud.wohlleben.dev
A
37.247.70.206
Parthenstein/Saxony/Germany (DE) - envia TEL GmbH
No Hostname found
yes
1
0

AAAA

yes


www.cloud.wohlleben.dev

Name Error
yes
1
0
*.wohlleben.dev
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.cloud.wohlleben.dev
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=






• Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 11019, Flags 256






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






Public Key with Algorithm 8, KeyTag 46780, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 10.10.2023, 00:00:00 +, Signature-Inception: 19.09.2023, 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: dev

dev
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 60074, DigestType 2 and Digest uULizlrr9i/KWdBXB+bbt5UhHVQNitugLp6J6DNCR4U=






1 RRSIG RR to validate DS RR found






RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 11.10.2023, 13:00:00 +, Signature-Inception: 28.09.2023, 12:00:00 +, KeyTag 11019, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 48661, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 17.10.2023, 21:05:24 +, Signature-Inception: 25.09.2023, 21:05:24 +, KeyTag 60074, Signer-Name: dev






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






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



Zone: wohlleben.dev

wohlleben.dev
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 "1ckrcgervtaraf52mddgigdbq9hrh2ng" between the hashed NSEC3-owner "1ckrcgervtaraf52mddgigdbq9hrh2ng" and the hashed NextOwner "1cktoa1d8gpvmbb08sa3prc69d3toet0". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner 1ckrcgervtaraf52mddgigdbq9hrh2ng.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 17.10.2023, 21:05:24 +, Signature-Inception: 25.09.2023, 21:05:24 +, KeyTag 48661, Signer-Name: dev






0 DNSKEY RR found









Zone: cloud.wohlleben.dev

cloud.wohlleben.dev
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.cloud.wohlleben.dev

www.cloud.wohlleben.dev
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.cloud.wohlleben.dev
•  ns53.domaincontrol.com

cloud.wohlleben.dev
•  ns53.domaincontrol.com / hex:0D 70 31 35
97.74.106.27
Tempe/Arizona/United States (US) - Host Europe GmbH		•

• 
2603:5:21a2::1b
Tempe/Arizona/United States (US) - Host Europe GmbH		•
wohlleben.dev
•  ns53.domaincontrol.com / hex:0D 70 31 35
97.74.106.27
Tempe/Arizona/United States (US) - Host Europe GmbH		•

• 
2603:5:21a2::1b
Tempe/Arizona/United States (US) - Host Europe GmbH		•

•  ns54.domaincontrol.com / hex:0D 70 31 34
173.201.74.27
Tempe/Arizona/United States (US) - Host Europe GmbH		•

• 
2603:5:22a2::1b
Tempe/Arizona/United States (US) - Host Europe GmbH		•
dev
•  ns-tld1.charlestonroadregistry.com
•

•  ns-tld2.charlestonroadregistry.com
•

•  ns-tld3.charlestonroadregistry.com
•

•  ns-tld4.charlestonroadregistry.com
•

•  ns-tld5.charlestonroadregistry.com
•

 

4. SOA-Entries


Domain:dev
Zone-Name:dev
Primary:ns-tld1.charlestonroadregistry.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:5


Domain:wohlleben.dev
Zone-Name:wohlleben.dev
Primary:ns53.domaincontrol.com
Mail:dns.jomax.net
Serial:2023041004
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:4


Domain:cloud.wohlleben.dev
Zone-Name:wohlleben.dev
Primary:ns53.domaincontrol.com
Mail:dns.jomax.net
Serial:2023041004
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:2


Domain:www.cloud.wohlleben.dev
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

Startaddress: https://cloud.wohlleben.dev/, address used: https://cloud.wohlleben.dev/index.php/login, Screenshot created 2023-09-28 18:53:16 +00:0

 

Mobil (412px x 732px)

 

1018 milliseconds

 

Screenshot mobile - https://cloud.wohlleben.dev/index.php/login
Mobil + Landscape (732px x 412px)

 

971 milliseconds

 

Screenshot mobile landscape - https://cloud.wohlleben.dev/index.php/login
Screen (1280px x 1680px)

 

4270 milliseconds

 

Screenshot Desktop - https://cloud.wohlleben.dev/index.php/login

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport412732
content Size412732

 

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://cloud.wohlleben.dev/
37.247.70.206
301
https://cloud.wohlleben.dev/
Html is minified: 109.03 %
0.100
A
Server: nginx/1.18.0
Date: Thu, 28 Sep 2023 16:51:41 GMT
Content-Type: text/html
Content-Length: 169
Connection: close
Location: https://cloud.wohlleben.dev/

• https://cloud.wohlleben.dev/
37.247.70.206
Inline-JavaScript (∑/total): 1/33 Inline-CSS (∑/total): 0/0		200

Html is minified: 156.00 %
Other inline scripts (∑/total): 1/33		2.590
A
small visible content (num chars: 15)
<!DOCTYPE html>
Server: nginx/1.18.0
Date: Thu, 28 Sep 2023 16:51:41 GMT
Content-Type: text/html
Content-Length: 144
Connection: close
Last-Modified: Thu, 24 Aug 2023 11:14:35 GMT
ETag: "9c-603a9554e0ce7-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Strict-Transport-Security: max-age=31536000; includeSubDomains

• http://cloud.wohlleben.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
37.247.70.206
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		301
https://cloud.wohlleben.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 109.03 %
Other inline scripts (∑/total): 0/0		0.206
A
Visible Content: 301 Moved Permanently nginx/1.18.0
Server: nginx/1.18.0
Date: Thu, 28 Sep 2023 16:51:46 GMT
Content-Type: text/html
Content-Length: 169
Connection: close
Location: https://cloud.wohlleben.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• https://cloud.wohlleben.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 100.00 %
Other inline scripts (∑/total): 0/0		2.544
A
Not Found
Visible Content: Not Found The requested URL was not found on this server. Apache/2.4.56 (Debian) Server at cloud.wohlleben.dev Port 80
Server: nginx/1.18.0
Date: Thu, 28 Sep 2023 16:51:50 GMT
Content-Type: text/html; charset=iso-8859-1
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://37.247.70.206/
37.247.70.206
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		200

Html is minified: 103.77 %
Other inline scripts (∑/total): 0/0		2.530
N
Certificate error: RemoteCertificateNameMismatch
small visible content (num chars: 38)
Hello and good bye from wohlleben.dev!
Server: nginx/1.18.0
Date: Thu, 28 Sep 2023 16:51:46 GMT
Content-Type: text/html
Last-Modified: Mon, 10 Apr 2023 12:34:19 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"6434024b-37"
Strict-Transport-Security: max-age=31536000; includeSubDomains
Content-Encoding: gzip

 

7. Comments


1. General Results, most used to calculate the result

Aname "cloud.wohlleben.dev" is subdomain, public suffix is ".dev", top-level-domain is ".dev", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .dev-domains preloaded: 14 (complete: 231048)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: cloud.wohlleben.dev has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: cloud.wohlleben.dev has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: No cookie sent via http.
AExcellent: Main Domain is in the Google-Preload-List
AExcellent: Main Domain is in the Mozilla/Firefox-Preload-List
AHSTS-Preload-Status: Preloaded. 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):1 complete Content-Type - header (3 urls)
https://cloud.wohlleben.dev/ 37.247.70.206


Url with incomplete Content-Type - header - missing charset
https://37.247.70.206/ 37.247.70.206


Url with incomplete Content-Type - header - missing charset
Ahttp://cloud.wohlleben.dev/ 37.247.70.206
301
https://cloud.wohlleben.dev/
Correct redirect http - https with the same domain name
Bhttps://cloud.wohlleben.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404

Missing HSTS-Header
Nhttps://37.247.70.206/ 37.247.70.206
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain cloud.wohlleben.dev, 1 ip addresses, 1 different http results.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.cloud.wohlleben.dev

2. Header-Checks

Fcloud.wohlleben.dev 37.247.70.206
Content-Security-Policy
Critical: Missing Header:
Fcloud.wohlleben.dev 37.247.70.206
X-Content-Type-Options
Critical: Missing Header:
Fcloud.wohlleben.dev 37.247.70.206
Referrer-Policy
Critical: Missing Header:
Fcloud.wohlleben.dev 37.247.70.206
Permissions-Policy
Critical: Missing Header:

3. DNS- and NameServer - Checks

AInfo:: 47 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 47 Queries complete, 47 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 23.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns53.domaincontrol.com, ns54.domaincontrol.com, 2 Name Servers included in Delegation: ns53.domaincontrol.com, ns54.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns53.domaincontrol.com, ns54.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns53.domaincontrol.com.
AGood: Only one SOA.Primary Name Server found.: ns53.domaincontrol.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns53.domaincontrol.com.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns53.domaincontrol.com, ns54.domaincontrol.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: domaincontrol.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 173., 97., 2 different subnets (first two Bytes): 173.201., 97.74., 2 different subnets (first three Bytes): 173.201.74., 97.74.106.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2603:, 1 different subnets (first two blocks): 2603:0005:, 2 different subnets (first three blocks): 2603:0005:21a2:, 2603:0005:22a2:, 2 different subnets (first four blocks): 2603:0005:21a2:0000:, 2603:0005:22a2:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns53.domaincontrol.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

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.
https://cloud.wohlleben.dev/ 37.247.70.206
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://cloud.wohlleben.dev/ 37.247.70.206
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://cloud.wohlleben.dev/ 37.247.70.206
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
https://37.247.70.206/ 37.247.70.206
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
AInfo: No img element found, no alt attribute checked
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
https://cloud.wohlleben.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
2.544 seconds
Warning: 404 needs more then one second
ADuration: 156003 milliseconds, 156.003 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
cloud.wohlleben.dev
37.247.70.206
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
cloud.wohlleben.dev
37.247.70.206
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=cloud.wohlleben.dev


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US


cloud.wohlleben.dev
cloud.wohlleben.dev
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

cloud.wohlleben.dev
cloud.wohlleben.dev
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
 Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=cloud.wohlleben.dev


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US


37.247.70.206
37.247.70.206
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

37.247.70.206
37.247.70.206
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=cloud.wohlleben.dev


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US

 

9. Certificates

1.
1.
CN=cloud.wohlleben.dev
09.08.2023
07.11.2023
557 days expired		cloud.wohlleben.dev, gsp.wohlleben.dev, wohlleben.dev, www.wohlleben.dev - 4 entries
1.
1.
CN=cloud.wohlleben.dev
09.08.2023

07.11.2023
557 days expired


cloud.wohlleben.dev, gsp.wohlleben.dev, wohlleben.dev, www.wohlleben.dev - 4 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03C5DF356D82C1E767975110D958F7EA2127
Thumbprint:41B379BC5B9B4B306CE8277F41D99119EF94352A
SHA256 / Certificate:4Xch3qOR2zEtcUXWr34e8TofzliJLQo0p0VcGdIwDoY=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):911d023e73dfca6b5fe669667bd208a99b09cdd6326f015155efe9ae4b599ae0
SHA256 hex / Subject Public Key Information (SPKI):911d023e73dfca6b5fe669667bd208a99b09cdd6326f015155efe9ae4b599ae0 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://r3.o.lencr.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020
15.09.2025
expires in 121 days

2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020

15.09.2025
expires in 121 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00912B084ACF0C18A753F6D62E25A75F5A
Thumbprint:A053375BFE84E8B748782C7CEE15827A6AF5A405
SHA256 / Certificate:Z63RFmsCCuYbj1/JaBPATCqliZYHloZVcqPH5zdhPf0=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SHA256 hex / Subject Public Key Information (SPKI):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3670 days

3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015

04.06.2035
expires in 3670 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
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
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
5658037456
leaf cert		CN=R3, O=Let's Encrypt, C=US
2023-08-09 10:48:22
2023-11-07 10:48:21
cloud.wohlleben.dev, gsp.wohlleben.dev, wohlleben.dev, www.wohlleben.dev - 4 entries


 

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

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

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
10235739542
leaf cert		CN=R3, O=Let's Encrypt, C=US
2023-08-09 08:48:22
2023-11-07 09:48:21
cloud.wohlleben.dev, gsp.wohlleben.dev, wohlleben.dev, www.wohlleben.dev
4 entries


9637545508
leaf cert		CN=R3, O=Let's Encrypt, C=US
2023-06-09 18:35:46
2023-09-07 18:35:45
cloud.wohlleben.dev, gsp.wohlleben.dev, wohlleben.dev, www.wohlleben.dev
4 entries


 

11. Html-Content - Entries

Summary


Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://cloud.wohlleben.dev/
37.247.70.206		meta
other
1

0


0
0
0

 

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

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsg∑Status
https://cloud.wohlleben.dev/
37.247.70.206
meta
refresh
0; URL=index.php


1
ok














 

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: ns53.domaincontrol.com, ns54.domaincontrol.com

 

QNr.DomainTypeNS used
1
com
NS
e.root-servers.net (2001:500:a8::e)

Answer: 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
2
ns53.domaincontrol.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
3
ns54.domaincontrol.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
4
net
NS
a.root-servers.net (2001:503:ba3e::2:30)

Answer: 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
5
a1-245.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
6
a11-64.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
7
a20-65.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
8
a6-66.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
9
a8-67.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
10
a1-67.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
11
a11-67.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
12
a12-67.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
13
a13-67.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
14
a22-67.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
15
a4-67.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
16
a6-67.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
17
a7-67.akam.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a3-67.akam.net
2600:1408:1c::43, 96.7.49.67

Answer: a5-67.akam.net
2600:1480:b000::43, 95.100.168.67

Answer: a9-67.akam.net
184.85.248.67, 2a02:26f0:117::43
18
a1-245.akam.net: 193.108.91.245
A
a18-67.akam.net (2600:1480:4800::43)
19
a1-245.akam.net: 2600:1401:2::f5
AAAA
a18-67.akam.net (2600:1480:4800::43)
20
a11-64.akam.net: 84.53.139.64
A
a18-67.akam.net (2600:1480:4800::43)
21
a11-64.akam.net: 2600:1480:1::40
AAAA
a18-67.akam.net (2600:1480:4800::43)
22
a20-65.akam.net: 95.100.175.65
A
a18-67.akam.net (2600:1480:4800::43)
23
a20-65.akam.net: 2a02:26f0:67::41
AAAA
a18-67.akam.net (2600:1480:4800::43)
24
a6-66.akam.net: 23.211.133.66
A
a18-67.akam.net (2600:1480:4800::43)
25
a6-66.akam.net: 2600:1401:1::42
AAAA
a18-67.akam.net (2600:1480:4800::43)
26
a8-67.akam.net: 2.16.40.67
A
a18-67.akam.net (2600:1480:4800::43)
27
a8-67.akam.net: 2600:1403:a::43
AAAA
a18-67.akam.net (2600:1480:4800::43)
28
a1-67.akam.net: 193.108.91.67
A
a18-67.akam.net (2600:1480:4800::43)
29
a1-67.akam.net: 2600:1401:2::43
AAAA
a18-67.akam.net (2600:1480:4800::43)
30
a11-67.akam.net: 84.53.139.67
A
a1-67.akam.net (2600:1401:2::43)
31
a11-67.akam.net: 2600:1480:1::43
AAAA
a1-67.akam.net (2600:1401:2::43)
32
a12-67.akam.net: 184.26.160.67
A
a1-67.akam.net (2600:1401:2::43)
33
a12-67.akam.net: 2600:1480:f000::43
AAAA
a1-67.akam.net (2600:1401:2::43)
34
a13-67.akam.net: 2.22.230.67
A
a1-67.akam.net (2600:1401:2::43)
35
a13-67.akam.net: 2600:1480:800::43
AAAA
a1-67.akam.net (2600:1401:2::43)
36
a22-67.akam.net: 23.211.61.67
A
a1-67.akam.net (2600:1401:2::43)
37
a22-67.akam.net: 2600:1480:7800::43
AAAA
a1-67.akam.net (2600:1401:2::43)
38
a4-67.akam.net: 72.246.46.67
A
a1-67.akam.net (2600:1401:2::43)
39
a4-67.akam.net: 2600:1480:9000::43
AAAA
a1-67.akam.net (2600:1401:2::43)
40
a6-67.akam.net: 23.211.133.67
A
a1-67.akam.net (2600:1401:2::43)
41
a6-67.akam.net: 2600:1401:1::43
AAAA
a1-67.akam.net (2600:1401:2::43)
42
a7-67.akam.net: 23.61.199.67
A
a1-67.akam.net (2600:1401:2::43)
43
a7-67.akam.net: 2600:1406:32::43
AAAA
a1-67.akam.net (2600:1401:2::43)
44
ns53.domaincontrol.com: 97.74.106.27
A
a1-245.akam.net (2600:1401:2::f5)
45
ns53.domaincontrol.com: 2603:5:21a2::1b
AAAA
a1-245.akam.net (2600:1401:2::f5)
46
ns54.domaincontrol.com: 173.201.74.27
A
a1-245.akam.net (2600:1401:2::f5)
47
ns54.domaincontrol.com: 2603:5:22a2::1b
AAAA
a1-245.akam.net (2600:1401:2::f5)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
cloud.wohlleben.dev
0

no CAA entry found
1
0
wohlleben.dev
0

no CAA entry found
1
0
dev
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
wohlleben.dev
v=spf1 include:outlook.com -all
ok
1
0
cloud.wohlleben.dev

ok
1
0
_acme-challenge.cloud.wohlleben.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.cloud.wohlleben.dev.wohlleben.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.cloud.wohlleben.dev.cloud.wohlleben.dev

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
cloud.wohlleben.dev
37.247.70.206
443
5 Ciphers52.33 sec
0 without, 5 FS
100.00 %
Complete

1
5 Ciphers
5.00 Ciphers/Check		52.33 sec52.33 sec/Check
0 without, 5 FS
100.00 %

Details
DomainIPPortCipher (OpenSsl / IANA)
cloud.wohlleben.dev
37.247.70.206
443
ECDHE-RSA-CHACHA20-POLY1305
 (Secure)
TLSv1.2
0xCC,0xA8
 FS
5 Ciphers, 52.33 sec
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

ECDH
RSA
CHACHA20/POLY1305(256)
AEAD




ECDHE-RSA-AES256-GCM-SHA384
 (Secure)
TLSv1.2
0xC0,0x30
 FS

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

ECDH
RSA
AESGCM(256)
AEAD




DHE-RSA-AES256-GCM-SHA384
 (Secure)
TLSv1.2
0x00,0x9F
 FS

TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

DH
RSA
AESGCM(256)
AEAD




ECDHE-RSA-AES128-GCM-SHA256
 (Secure)
TLSv1.2
0xC0,0x2F
 FS

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

ECDH
RSA
AESGCM(128)
AEAD




DHE-RSA-AES128-GCM-SHA256
 (Secure)
TLSv1.2
0x00,0x9E
 FS

TLS_DHE_RSA_WITH_AES_128_GCM_SHA256

DH
RSA
AESGCM(128)
AEAD

 

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

 

 

Permalink: https://check-your-website.server-daten.de/?i=09f04db7-9041-4bf5-a003-8350d73d18ca

 

Last Result: https://check-your-website.server-daten.de/?q=cloud.wohlleben.dev - 2023-09-28 18:51:01

 

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

 

<a href="https://check-your-website.server-daten.de/?q=cloud.wohlleben.dev" target="_blank">Check this Site: cloud.wohlleben.dev</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=cloud.wohlleben.dev

 

 

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