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

0 in Queue, 1 of max. 8 Checks (01:44:34)
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 |

 

N

 

No trusted Certificate

 

Checked:
16.05.2026 08:23:45

 

Older results

 

L - 16.05.2026 07:26:51

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
jocsandbonwedding.online
A
119.93.232.35
San Mateo/Calabarzon/Philippines (PH) - Philippine Long Distance Telephone Co.
Hostname: mail.redwood.ph
yes
2
0

AAAA

yes


www.jocsandbonwedding.online
CNAME
jocsandbonwedding.online
yes
1
0

A
119.93.232.35
San Mateo/Calabarzon/Philippines (PH) - Philippine Long Distance Telephone Co.
Hostname: mail.redwood.ph
yes


*.jocsandbonwedding.online
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 20326, Flags 257 (SEP = Secure Entry Point)






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






Public Key with Algorithm 8, KeyTag 54393, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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

online
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 30961, DigestType 2 and Digest kpLIsQQGaEsuiSCQFL9OFKyNJ371tvw2EisLWHis1H4=






1 RRSIG RR to validate DS RR found






RRSIG-Owner online., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 29.05.2026, 05:00:00 +, Signature-Inception: 16.05.2026, 04:00:00 +, KeyTag 54393, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 30961, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 13, KeyTag 34647, Flags 256






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner online., Algorithm: 13, 1 Labels, original TTL: 300 sec, Signature-expiration: 29.05.2026, 02:29:48 +, Signature-Inception: 29.04.2026, 20:18:51 +, KeyTag 30961, Signer-Name: online






RRSIG-Owner online., Algorithm: 13, 1 Labels, original TTL: 300 sec, Signature-expiration: 29.05.2026, 05:28:52 +, Signature-Inception: 29.04.2026, 20:18:51 +, KeyTag 34647, Signer-Name: online






• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 30961 used to validate the DNSKEY RRSet






• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 34647 used to validate the DNSKEY RRSet






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



Zone: jocsandbonwedding.online

jocsandbonwedding.online
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 "giet01vatki6ps9k4i3rrh4ciljjpv19" between the hashed NSEC3-owner "gierp2jm2gseu7bnk7r8noant427ptfn" and the hashed NextOwner "gif2df6aoheesj142eicu7rv97iruajj". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner gierp2jm2gseu7bnk7r8noant427ptfn.online., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 14.06.2026, 01:49:04 +, Signature-Inception: 15.05.2026, 21:58:40 +, KeyTag 34647, Signer-Name: online






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "1ribnbjb5koke6vekotivtq00v2eqsdj" as Owner. That's the Hash of "online" with the NextHashedOwnerName "1ribrldjvjp159c8u53mo352908f7e20". So that domain name is the Closest Encloser of "jocsandbonwedding.online". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 1ribnbjb5koke6vekotivtq00v2eqsdj.online., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 13.06.2026, 06:30:43 +, Signature-Inception: 15.05.2026, 17:58:56 +, KeyTag 34647, Signer-Name: online






0 DNSKEY RR found









Zone: www.jocsandbonwedding.online

www.jocsandbonwedding.online
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
jocsandbonwedding.online
•  ns13.domaincontrol.com / hex:0D 70 30 31
97.74.106.7
Tempe/Arizona/United States (US) - Host Europe GmbH		•

• 
2603:5:21a0::7
New York/United States (US) - Host Europe GmbH		•

•  ns14.domaincontrol.com / hex:0D 70 32 32
173.201.74.7
Tempe/Arizona/United States (US) - Host Europe GmbH		•

• 
2603:5:22a0::7
New York/United States (US) - Host Europe GmbH		•
online
•  ns.trs-dns.com


•  ns01.trs-dns.com / fra01.dns1
•

•  ns01.trs-dns.net / fra01.dns2
•

•  ns10.trs-dns.info / 1.fra.pch
•

•  ns10.trs-dns.org / 2.fra.pch
•

 

4. SOA-Entries


Domain:online
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:online
Zone-Name:online
Primary:ns.trs-dns.com
Mail:trs-ops.tucows.com
Serial:1778912313
Refresh:1800
Retry:900
Expire:604800
TTL:300
num Entries:4


Domain:jocsandbonwedding.online
Zone-Name:jocsandbonwedding.online
Primary:ns13.domaincontrol.com
Mail:dns.jomax.net
Serial:2026051502
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:4


5. Screenshots

Startaddress: https://jocsandbonwedding.online/, address used: https://jocsandbonwedding.online/, Screenshot created 2026-05-16 08:31:49 +00:0 url is insecure, certificate invalid

 

Mobil (412px x 732px)

 

1192 milliseconds

 

Screenshot mobile - https://jocsandbonwedding.online/
Mobil + Landscape (732px x 412px)

 

1223 milliseconds

 

Screenshot mobile landscape - https://jocsandbonwedding.online/
Screen (1280px x 1680px)

 

1249 milliseconds

 

Screenshot Desktop - https://jocsandbonwedding.online/

 

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://jocsandbonwedding.online/
119.93.232.35
301
http://www.jocsandbonwedding.online/

0.510
D
Location: http://www.jocsandbonwedding.online/
Content-Length: 0

• http://www.jocsandbonwedding.online/
119.93.232.35 No Compression used - 12551 / 59651 - 21.04 % possible
200

Html is minified: 229.44 %
0.773
H
Date: Sat, 16 May 2026 06:24:10 GMT
Server: Apache/2.4.67,(Win64)
ETag: "e903-651d36ecffa73"
Accept-Ranges: bytes
Last-Modified: Fri, 15 May 2026 04:13:19 GMT
Content-Length: 59651
Content-Type: text/html

• https://jocsandbonwedding.online/
119.93.232.35
400

Html is minified: 110.00 %
20.797
N
Bad Request
Certificate error: RemoteCertificateNameMismatch
Date: Sat, 16 May 2026 06:23:29 GMT
Server: Apache/2.4.41,(Win64),OpenSSL/1.1.1c,PHP/7.2.29,mod_wsgi/4.7.1,Python/3.8
X-Content-Type-Options: nosniff
Referrer-Policy: same-origin
Cross-Origin-Opener-Policy: same-origin
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8
Content-Length: 143

• https://www.jocsandbonwedding.online/
119.93.232.35
400

Html is minified: 110.00 %
16.863
N
Bad Request
Certificate error: RemoteCertificateNameMismatch
Date: Sat, 16 May 2026 06:23:52 GMT
Server: Apache/2.4.41,(Win64),OpenSSL/1.1.1c,PHP/7.2.29,mod_wsgi/4.7.1,Python/3.8
X-Content-Type-Options: nosniff
Referrer-Policy: same-origin
Cross-Origin-Opener-Policy: same-origin
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8
Content-Length: 143

• http://jocsandbonwedding.online/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
119.93.232.35
301
http://www.jocsandbonwedding.online/

2.403
D
Visible Content:
Location: http://www.jocsandbonwedding.online/
Content-Length: 0

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

Html is minified: 103.06 %
Other inline scripts (∑/total): 0/0		0.310
A
Not Found
Visible Content:
Date: Sat, 16 May 2026 06:24:53 GMT
Server: Apache/2.4.67,(Win64)
Content-Length: 236
Content-Type: text/html; charset=iso-8859-1

• https://119.93.232.35/
119.93.232.35
400

Html is minified: 110.00 %
18.494
N
Bad Request
Certificate error: RemoteCertificateNameMismatch
Date: Sat, 16 May 2026 06:24:14 GMT
Server: Apache/2.4.41,(Win64),OpenSSL/1.1.1c,PHP/7.2.29,mod_wsgi/4.7.1,Python/3.8
X-Content-Type-Options: nosniff
Referrer-Policy: same-origin
Cross-Origin-Opener-Policy: same-origin
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8
Content-Length: 143

 

7. Comments


1. General Results, most used to calculate the result

Aname "jocsandbonwedding.online" is domain, public suffix is ".online", top-level-domain is ".online", top-level-domain-type is "generic", tld-manager is "DotOnline Inc.", num .online-domains preloaded: 701 (complete: 276475)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: jocsandbonwedding.online has only one ip address.
Warning: Only one ip address found: www.jocsandbonwedding.online 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: jocsandbonwedding.online has no ipv6 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: www.jocsandbonwedding.online has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AGood - only one version with Http-Status 200
AGood: No cookie sent via http.
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):1 complete Content-Type - header (2 urls)
http://www.jocsandbonwedding.online/ 119.93.232.35


Url with incomplete Content-Type - header - missing charset
Bhttps://jocsandbonwedding.online/ 119.93.232.35
400

Missing HSTS-Header
Bhttps://www.jocsandbonwedding.online/ 119.93.232.35
400

Missing HSTS-Header
Dhttp://jocsandbonwedding.online/ 119.93.232.35
301
http://www.jocsandbonwedding.online/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://jocsandbonwedding.online/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 119.93.232.35
301
http://www.jocsandbonwedding.online/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
HFatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Mhttps://jocsandbonwedding.online/ 119.93.232.35
400

Misconfiguration - main pages should never send http status 400 - 499
Mhttps://www.jocsandbonwedding.online/ 119.93.232.35
400

Misconfiguration - main pages should never send http status 400 - 499
Mhttps://119.93.232.35/ 119.93.232.35
400

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://jocsandbonwedding.online/ 119.93.232.35
400

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Nhttps://www.jocsandbonwedding.online/ 119.93.232.35
400

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Nhttps://119.93.232.35/ 119.93.232.35
400

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 jocsandbonwedding.online, 1 ip addresses, 1 different http results.
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 www.jocsandbonwedding.online, 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.jocsandbonwedding.online

2. Header-Checks

Ajocsandbonwedding.online 119.93.232.35
X-Content-Type-Options
Ok: Header without syntax errors found: nosniff
A
Referrer-Policy
Ok: Header without syntax errors found: same-origin
A
Cross-Origin-Opener-Policy
Ok: Header without syntax errors found: same-origin
Awww.jocsandbonwedding.online 119.93.232.35
X-Content-Type-Options
Ok: Header without syntax errors found: nosniff
A
Referrer-Policy
Ok: Header without syntax errors found: same-origin
A
Cross-Origin-Opener-Policy
Ok: Header without syntax errors found: same-origin
Fjocsandbonwedding.online 119.93.232.35
Content-Security-Policy
Critical: Missing Header:
Fjocsandbonwedding.online 119.93.232.35
Permissions-Policy
Critical: Missing Header:
Bjocsandbonwedding.online 119.93.232.35
Cross-Origin-Embedder-Policy
Info: Missing Header
Bjocsandbonwedding.online 119.93.232.35
Cross-Origin-Resource-Policy
Info: Missing Header
Fwww.jocsandbonwedding.online 119.93.232.35
Content-Security-Policy
Critical: Missing Header:
Fwww.jocsandbonwedding.online 119.93.232.35
Permissions-Policy
Critical: Missing Header:
Bwww.jocsandbonwedding.online 119.93.232.35
Cross-Origin-Embedder-Policy
Info: Missing Header
Bwww.jocsandbonwedding.online 119.93.232.35
Cross-Origin-Resource-Policy
Info: Missing Header

3. DNS- and NameServer - Checks

AInfo:: 26 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 26 Queries complete, 26 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 13.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns13.domaincontrol.com, ns14.domaincontrol.com, 2 Name Servers included in Delegation: ns13.domaincontrol.com, ns14.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns13.domaincontrol.com, ns14.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns13.domaincontrol.com.
AGood: Only one SOA.Primary Name Server found.: ns13.domaincontrol.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns13.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: ns13.domaincontrol.com, ns14.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:21a0:, 2603:0005:22a0:, 2 different subnets (first four blocks): 2603:0005:21a0:0000:, 2603:0005:22a0:0000:
AGood: Name Server IPv6 addresses from different subnets found.
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
Nameserver doesn't pass all EDNS-Checks: ns.trs-dns.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.
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
AInfo: Different Server-Headers found
ADuration: 489777 milliseconds, 489.777 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
jocsandbonwedding.online
119.93.232.35
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
jocsandbonwedding.online
119.93.232.35
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
no Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
 no Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=darpoldn.ddns.net


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


www.jocsandbonwedding.online
119.93.232.35
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

www.jocsandbonwedding.online
119.93.232.35
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
no Tls.1.2
no Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
 no Tls.1.2
no Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=darpoldn.ddns.net


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


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

119.93.232.35
119.93.232.35
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
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
Cert sent without SNI 		Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=darpoldn.ddns.net


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

 

9. Certificates

1.
1.
CN=darpoldn.ddns.net
15.05.2026
13.08.2026
expires in 66 days		darpoldn.ddns.net, dawat-darpoldn.ddns.net - 2 entries
1.
1.
CN=darpoldn.ddns.net
15.05.2026

13.08.2026
expires in 66 days


darpoldn.ddns.net, dawat-darpoldn.ddns.net - 2 entries

KeyalgorithmEC Public Key (256 bit, prime256v1)
Signatur:ECDSA SHA384
Serial Number:06000AD6F83A3CA0C28F7F064872091E29AE
Thumbprint:E819DBE875458F012E70A7B386B53D7E2C1068EE
SHA256 / Certificate:PLsaAJlICahblQIYrnXPogm2MyPtrj69KD8zgGGPxEA=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):fadeacb46149596efe1f877a9e4c168e9c5d8449a302473e7cade1d953e2950f
SHA256 hex / Subject Public Key Information (SPKI):fadeacb46149596efe1f877a9e4c168e9c5d8449a302473e7cade1d953e2950f (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




2.
CN=E7, O=Let's Encrypt, C=US
13.03.2024
13.03.2027
expires in 278 days

2.
CN=E7, O=Let's Encrypt, C=US
13.03.2024

13.03.2027
expires in 278 days




KeyalgorithmEC Public Key (384 bit, secp384r1)
Signatur:SHA256 With RSA-Encryption
Serial Number:00AA75F1E62B8F0A220966D38BBFD4BAA1
Thumbprint:3B73C17E3DF87CF3AA77F1389219EB5EDD519E7F
SHA256 / Certificate:rrH9dBDoO8lvXaPGp8LBu4NtH6XLhucIUViQ5Ciodws=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):cbbc559b44d524d6a132bdac672744da3407f12aae5d5f722c5f6c7913871c75
SHA256 hex / Subject Public Key Information (SPKI):
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 3283 days

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

04.06.2035
expires in 3283 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)

No CertSpotter - CT-Log entries found

 

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

No Html-Content entries found. Only checked if https + status 200/401/403/404

 

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


No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns13.domaincontrol.com, ns14.domaincontrol.com

 

QNr.DomainTypeNS used
1
com
NS
k.root-servers.net (2001:7fd::1)

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
ns13.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
ns14.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
k.root-servers.net (2001:7fd::1)

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

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

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

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

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

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67

Answer: a6-67.akam.net
23.211.133.67, 2600:1401:1::43
6
a11-64.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

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

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

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

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67

Answer: a6-67.akam.net
23.211.133.67, 2600:1401:1::43
7
a20-65.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

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

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

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

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67

Answer: a6-67.akam.net
23.211.133.67, 2600:1401:1::43
8
a6-66.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

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

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

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

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67

Answer: a6-67.akam.net
23.211.133.67, 2600:1401:1::43
9
a8-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

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

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

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

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67

Answer: a6-67.akam.net
23.211.133.67, 2600:1401:1::43
10
a9-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

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

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

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

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67

Answer: a6-67.akam.net
23.211.133.67, 2600:1401:1::43
11
a1-245.akam.net: 193.108.91.245
A
a1-67.akam.net (2600:1401:2::43)
12
a1-245.akam.net: 2600:1401:2::f5
AAAA
a1-67.akam.net (2600:1401:2::43)
13
a11-64.akam.net: 84.53.139.64
A
a1-67.akam.net (2600:1401:2::43)
14
a11-64.akam.net: 2600:1480:1::40
AAAA
a1-67.akam.net (2600:1401:2::43)
15
a20-65.akam.net: 95.100.175.65
A
a1-67.akam.net (2600:1401:2::43)
16
a20-65.akam.net: 2a02:26f0:67::41
AAAA
a1-67.akam.net (2600:1401:2::43)
17
a6-66.akam.net: 23.211.133.66
A
a1-67.akam.net (2600:1401:2::43)
18
a6-66.akam.net: 2600:1401:1::42
AAAA
a1-67.akam.net (2600:1401:2::43)
19
a8-67.akam.net: 2.16.40.67
A
a1-67.akam.net (2600:1401:2::43)
20
a8-67.akam.net: 2600:1403:a::43
AAAA
a1-67.akam.net (2600:1401:2::43)
21
a9-67.akam.net: 184.85.248.67
A
a1-67.akam.net (2600:1401:2::43)
22
a9-67.akam.net: 2a02:26f0:117::43
AAAA
a1-67.akam.net (2600:1401:2::43)
23
ns13.domaincontrol.com: 97.74.106.7
A
a1-245.akam.net (2600:1401:2::f5)
24
ns13.domaincontrol.com: 2603:5:21a0::7
AAAA
a1-245.akam.net (2600:1401:2::f5)
25
ns14.domaincontrol.com: 173.201.74.7
A
a1-245.akam.net (2600:1401:2::f5)
26
ns14.domaincontrol.com: 2603:5:22a0::7
AAAA
a1-245.akam.net (2600:1401:2::f5)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.jocsandbonwedding.online



1
0
jocsandbonwedding.online
0

no CAA entry found
1
0
online
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
jocsandbonwedding.online

ok
1
0
www.jocsandbonwedding.online


1
0
_acme-challenge.jocsandbonwedding.online
Q14X-YCcohPR9mS01CDVIphOeRBQCcfsFt7jJW2ImXc
looks good, correct length, correct characters
1
0
_acme-challenge.www.jocsandbonwedding.online

Name Error - The domain name does not exist
1
0
_acme-challenge.jocsandbonwedding.online.jocsandbonwedding.online

Name Error - The domain name does not exist
1
0
_acme-challenge.www.jocsandbonwedding.online.jocsandbonwedding.online

Name Error - The domain name does not exist
1
0
_acme-challenge.www.jocsandbonwedding.online.www.jocsandbonwedding.online

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
_dmarc
TXT
_dmarc.jocsandbonwedding.online

v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;
ok

TXT
jocsandbonwedding.online._report._dmarc.onsecureserver.net

mailto:dmarc_rua@onsecureserver.net
okMail domain unequal current domain. Check required, if there is a confirming _report._dmarc-Record. See RFC 7489, 7.1.

TXT
jocsandbonwedding.online._report._dmarc.onsecureserver.net

v=DMARC1
okConfirmed. Sending reports to external domain is allowed.

 

 

17. Cipher Suites

Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
jocsandbonwedding.online
119.93.232.35
443
14 Ciphers184.04 sec
0 without, 14 FS
100.00 %
www.jocsandbonwedding.online
119.93.232.35
443
12 Ciphers190.25 sec
0 without, 12 FS
100.00 %
Complete

2
26 Ciphers
13.00 Ciphers/Check		374.29 sec187.15 sec/Check
0 without, 26 FS
100.00 %

Details
DomainIPPortCipher (OpenSsl / IANA)
jocsandbonwedding.online
119.93.232.35
443
ECDHE-ECDSA-AES256-GCM-SHA384
 (Recommended)
TLSv1.2
0xC0,0x2C
 FS
14 Ciphers, 184.04 sec
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

ECDH
ECDSA
AESGCM(256)
AEAD




ECDHE-ECDSA-AES128-GCM-SHA256
 (Recommended)
TLSv1.2
0xC0,0x2B
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

ECDH
ECDSA
AESGCM(128)
AEAD




ECDHE-ECDSA-AES256-CCM8
 (Secure)
TLSv1.2
0xC0,0xAF
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_CCM_8

ECDH
ECDSA
AESCCM8(256)
AEAD




ECDHE-ECDSA-AES256-CCM
 (Secure)
TLSv1.2
0xC0,0xAD
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_CCM

ECDH
ECDSA
AESCCM(256)
AEAD




ECDHE-ECDSA-AES128-CCM8
 (Secure)
TLSv1.2
0xC0,0xAE
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8

ECDH
ECDSA
AESCCM8(128)
AEAD




ECDHE-ECDSA-AES128-CCM
 (Secure)
TLSv1.2
0xC0,0xAC
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_CCM

ECDH
ECDSA
AESCCM(128)
AEAD




ECDHE-ECDSA-CAMELLIA256-SHA384
 (Weak)
TLSv1.2
0xC0,0x73
 FS

TLS_ECDHE_ECDSA_WITH_CAMELLIA_256_CBC_SHA384

ECDH
ECDSA
Camellia(256)
SHA384




ECDHE-ECDSA-ARIA256-GCM-SHA384
 (Weak)
TLSv1.2
0xC0,0x5D
 FS

TLS_ECDHE_ECDSA_WITH_ARIA_256_GCM_SHA384

ECDH
ECDSA
ARIAGCM(256)
AEAD




ECDHE-ECDSA-AES256-SHA384
 (Weak)
TLSv1.2
0xC0,0x24
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384

ECDH
ECDSA
AES(256)
SHA384




ECDHE-ECDSA-CAMELLIA128-SHA256
 (Weak)
TLSv1.2
0xC0,0x72
 FS

TLS_ECDHE_ECDSA_WITH_CAMELLIA_128_CBC_SHA256

ECDH
ECDSA
Camellia(128)
SHA256




ECDHE-ECDSA-ARIA128-GCM-SHA256
 (Weak)
TLSv1.2
0xC0,0x5C
 FS

TLS_ECDHE_ECDSA_WITH_ARIA_128_GCM_SHA256

ECDH
ECDSA
ARIAGCM(128)
AEAD




ECDHE-ECDSA-AES128-SHA256
 (Weak)
TLSv1.2
0xC0,0x23
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256

ECDH
ECDSA
AES(128)
SHA256




ECDHE-ECDSA-AES256-SHA
 (Weak)
TLSv1
0xC0,0x0A
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA

ECDH
ECDSA
AES(256)
SHA1




ECDHE-ECDSA-AES128-SHA
 (Weak)
TLSv1
0xC0,0x09
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA

ECDH
ECDSA
AES(128)
SHA1

www.jocsandbonwedding.online
119.93.232.35
443
ECDHE-ECDSA-CHACHA20-POLY1305
 (Recommended)
TLSv1.2
0xCC,0xA9
 FS
12 Ciphers, 190.25 sec
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256

ECDH
ECDSA
CHACHA20/POLY1305(256)
AEAD




ECDHE-ECDSA-AES128-GCM-SHA256
 (Recommended)
TLSv1.2
0xC0,0x2B
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

ECDH
ECDSA
AESGCM(128)
AEAD




ECDHE-ECDSA-AES256-CCM8
 (Secure)
TLSv1.2
0xC0,0xAF
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_CCM_8

ECDH
ECDSA
AESCCM8(256)
AEAD




ECDHE-ECDSA-AES256-CCM
 (Secure)
TLSv1.2
0xC0,0xAD
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_CCM

ECDH
ECDSA
AESCCM(256)
AEAD




ECDHE-ECDSA-AES128-CCM8
 (Secure)
TLSv1.2
0xC0,0xAE
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8

ECDH
ECDSA
AESCCM8(128)
AEAD




ECDHE-ECDSA-AES128-CCM
 (Secure)
TLSv1.2
0xC0,0xAC
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_CCM

ECDH
ECDSA
AESCCM(128)
AEAD




ECDHE-ECDSA-AES256-SHA384
 (Weak)
TLSv1.2
0xC0,0x24
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384

ECDH
ECDSA
AES(256)
SHA384




ECDHE-ECDSA-CAMELLIA128-SHA256
 (Weak)
TLSv1.2
0xC0,0x72
 FS

TLS_ECDHE_ECDSA_WITH_CAMELLIA_128_CBC_SHA256

ECDH
ECDSA
Camellia(128)
SHA256




ECDHE-ECDSA-ARIA128-GCM-SHA256
 (Weak)
TLSv1.2
0xC0,0x5C
 FS

TLS_ECDHE_ECDSA_WITH_ARIA_128_GCM_SHA256

ECDH
ECDSA
ARIAGCM(128)
AEAD




ECDHE-ECDSA-AES128-SHA256
 (Weak)
TLSv1.2
0xC0,0x23
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256

ECDH
ECDSA
AES(128)
SHA256




ECDHE-ECDSA-AES256-SHA
 (Weak)
TLSv1
0xC0,0x0A
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA

ECDH
ECDSA
AES(256)
SHA1




ECDHE-ECDSA-AES128-SHA
 (Weak)
TLSv1
0xC0,0x09
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA

ECDH
ECDSA
AES(128)
SHA1

 

18. Portchecks

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

 

 

Permalink: https://check-your-website.server-daten.de/?i=862ae806-88ff-4a33-9c82-b440d245c6e3

 

Last Result: https://check-your-website.server-daten.de/?q=jocsandbonwedding.online - 2026-05-16 08:23:45

 

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

 

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

 

 

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