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




P

Tls-Protocol error

Checked:
11.06.2024 13:45:31


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
casinolovepot.com
A
3.33.130.190
Toronto/Ontario/Canada (CA) - Amazon.com, Inc.
Hostname: a2aa9ff50de748dbe.awsglobalaccelerator.com
yes
2
0

A
15.197.148.33
Ashburn/Virginia/United States (US) - Amazon.com, Inc.
Hostname: a2aa9ff50de748dbe.awsglobalaccelerator.com
yes
2
0

A
34.125.66.187
Las Vegas/Nevada/United States (US) - Google LLC
Hostname: 187.66.125.34.bc.googleusercontent.com
yes
2
0

AAAA

yes


www.casinolovepot.com
CNAME
casinolovepot.com
yes
1
0

A
3.33.130.190
Toronto/Ontario/Canada (CA) - Amazon.com, Inc.
Hostname: a2aa9ff50de748dbe.awsglobalaccelerator.com
yes



A
15.197.148.33
Ashburn/Virginia/United States (US) - Amazon.com, Inc.
Hostname: a2aa9ff50de748dbe.awsglobalaccelerator.com
yes



A
34.125.66.187
Las Vegas/Nevada/United States (US) - Google LLC
Hostname: 187.66.125.34.bc.googleusercontent.com
yes


*.casinolovepot.com
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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 5613, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.07.2024, 00:00:00 +, Signature-Inception: 10.06.2024, 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: com
com
1 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.06.2024, 05:00:00 +, Signature-Inception: 11.06.2024, 04:00:00 +, KeyTag 5613, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 956, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 21.06.2024, 14:02:35 +, Signature-Inception: 06.06.2024, 13:57:35 +, KeyTag 19718, Signer-Name: com



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



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

Zone: casinolovepot.com
casinolovepot.com
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 "vb95isfh3colnckgv1oubet507b6s9vv" between the hashed NSEC3-owner "vb95ggq1fq7reb8tdqoorhl9khbg368m" and the hashed NextOwner "vb95mbbheit1pgngl3h2i6o64d34lk8d". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner vb95ggq1fq7reb8tdqoorhl9khbg368m.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.06.2024, 06:10:33 +, Signature-Inception: 09.06.2024, 05:00:33 +, KeyTag 956, Signer-Name: com



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q2d6ni4i7eqh8na30ns61o48ul8g5". So that domain name is the Closest Encloser of "casinolovepot.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 17.06.2024, 04:25:19 +, Signature-Inception: 10.06.2024, 03:15:19 +, KeyTag 956, Signer-Name: com



0 DNSKEY RR found




Zone: www.casinolovepot.com
www.casinolovepot.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
casinolovepot.com
  ns63.domaincontrol.com / hex:0D 70 31 37
97.74.101.42
Tempe/Arizona/United States (US) - Host Europe GmbH


 
2603:5:2154::2a
Chicago/Illinois/United States (US) - Host Europe GmbH


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


 
2603:5:2254::2a
Chicago/Illinois/United States (US) - Host Europe GmbH

com
  a.gtld-servers.net / nnn1-defra-5


  b.gtld-servers.net / nnn1-elvie2


  c.gtld-servers.net / nnn1-par6


  d.gtld-servers.net / nnn1-par6


  e.gtld-servers.net / nnn1-par6


  f.gtld-servers.net / nnn1-defra-4


  g.gtld-servers.net / nnn1-defra-4


  h.gtld-servers.net / nnn1-defra-4


  i.gtld-servers.net / nnn1-defra-4


  j.gtld-servers.net / nnn1-frmrs-2


  k.gtld-servers.net / nnn1-frmrs-2


  l.gtld-servers.net / nnn1-frmrs-2


  m.gtld-servers.net / nnn1-frmrs-2


4. SOA-Entries


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


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


Domain:casinolovepot.com
Zone-Name:casinolovepot.com
Primary:ns63.domaincontrol.com
Mail:dns.jomax.net
Serial:2024061000
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:4


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://casinolovepot.com/
34.125.66.187
302
http://casinolovepot.com/wp-admin/setup-config.php
0.323
D
Server: nginx
Date: Tue, 11 Jun 2024 11:46:15 GMT
Connection: close
Location: http://casinolovepot.com/wp-admin/setup-config.php
Content-Type: text/html; charset=UTF-8
Content-Length: 0

• http://www.casinolovepot.com/
34.125.66.187
302
http://www.casinolovepot.com/wp-admin/setup-config.php
0.326
D
Server: nginx
Date: Tue, 11 Jun 2024 11:46:16 GMT
Connection: close
Location: http://www.casinolovepot.com/wp-admin/setup-config.php
Content-Type: text/html; charset=UTF-8
Content-Length: 0

• http://casinolovepot.com/
3.33.130.190
200

Html is minified: 278.05 %
0.200
H
Server: openresty
Date: Tue, 11 Jun 2024 11:46:15 GMT
Connection: close
Content-Type: text/html
Content-Length: 114

• http://casinolovepot.com/
15.197.148.33
200

Html is minified: 278.05 %
7.424
H
Server: openresty
Date: Tue, 11 Jun 2024 11:46:15 GMT
Connection: close
Content-Type: text/html
Content-Length: 114

• http://www.casinolovepot.com/
3.33.130.190
200

Html is minified: 278.05 %
0.200
H
Server: openresty
Date: Tue, 11 Jun 2024 11:46:16 GMT
Connection: close
Content-Type: text/html
Content-Length: 114

• http://www.casinolovepot.com/
15.197.148.33
200

Html is minified: 278.05 %
0.200
H
Server: openresty
Date: Tue, 11 Jun 2024 11:46:16 GMT
Connection: close
Content-Type: text/html
Content-Length: 114

• http://casinolovepot.com/wp-admin/setup-config.php

200

Html is minified: 278.05 %
0.213
H
Server: openresty
Date: Tue, 11 Jun 2024 11:46:44 GMT
Connection: close
Content-Type: text/html
Content-Length: 114

• http://www.casinolovepot.com/wp-admin/setup-config.php

200

Html is minified: 278.05 %
0.214
H
Server: openresty
Date: Tue, 11 Jun 2024 11:46:44 GMT
Connection: close
Content-Type: text/html
Content-Length: 114

• https://casinolovepot.com/
34.125.66.187
301
http://casinolovepot.com/
Html is minified: 109.46 %
5.050
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Server: nginx
Date: Tue, 11 Jun 2024 11:46:17 GMT
Connection: close
Location: http://casinolovepot.com/
Content-Type: text/html
Content-Length: 162

• https://www.casinolovepot.com/
34.125.66.187
301
http://www.casinolovepot.com/
Html is minified: 109.46 %
5.003
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Server: nginx
Date: Tue, 11 Jun 2024 11:46:24 GMT
Connection: close
Location: http://www.casinolovepot.com/
Content-Type: text/html
Content-Length: 162

• https://casinolovepot.com/
3.33.130.190
-16

0.226
P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT).

• https://casinolovepot.com/
15.197.148.33
-16

0.263
P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT).

• https://www.casinolovepot.com/
3.33.130.190
-16

0.290
P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT).

• https://www.casinolovepot.com/
15.197.148.33
-16

0.216
P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT).

• http://casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
3.33.130.190
-16

0.807
W
UnknownError - An error occurred while sending the request.
Visible Content:

• http://casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
15.197.148.33
-16

4.860
W
UnknownError - An error occurred while sending the request.
Visible Content:

• http://casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.125.66.187
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 100.00 %
0.314
A
Visible Content:
Server: nginx
Date: Tue, 11 Jun 2024 11:46:35 GMT
Connection: close
Content-Type: text/plain; charset=utf-8
Content-Length: 86

• http://www.casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
3.33.130.190
-16

0.800
W
UnknownError - An error occurred while sending the request.
Visible Content:

• http://www.casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
15.197.148.33
-16

0.817
W
UnknownError - An error occurred while sending the request.
Visible Content:

• http://www.casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.125.66.187
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 100.00 %
0.316
A
Visible Content:
Server: nginx
Date: Tue, 11 Jun 2024 11:46:37 GMT
Connection: close
Content-Type: text/plain; charset=utf-8
Content-Length: 86

• http://34.125.66.187/
GZip used - 1085 / 2588 - 58.08 %
200

Html is minified: 255.73 %
0.324
H
Server: nginx
Date: Tue, 11 Jun 2024 11:46:45 GMT
Connection: close
ETag: "a1c-61a8a86f8606e-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 1085
Last-Modified: Mon, 10 Jun 2024 15:08:52 GMT
Content-Encoding: gzip

• https://34.125.66.187/
34.125.66.187
301
http://34.125.66.187/
Html is minified: 109.46 %
5.020
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Server: nginx
Date: Tue, 11 Jun 2024 11:46:39 GMT
Connection: close
Location: http://34.125.66.187/
Content-Type: text/html
Content-Length: 162

• https://3.33.130.190/
3.33.130.190
-16

0.216
P
UnknownError - The SSL connection could not be established, see inner exception. - Received an unexpected EOF or 0 bytes from the transport stream (FF: PR_END_OF_FILE_ERROR)

• https://15.197.148.33/
15.197.148.33
-16

0.216
P
UnknownError - The SSL connection could not be established, see inner exception. - Received an unexpected EOF or 0 bytes from the transport stream (FF: PR_END_OF_FILE_ERROR)

7. Comments


1. General Results, most used to calculate the result

Aname "casinolovepot.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 94787 (complete: 245733)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: casinolovepot.com has 3 different ip addresses (authoritative).
AGood: Minimal 2 ip addresses per domain name found: www.casinolovepot.com has 3 different ip addresses (authoritative).
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: casinolovepot.com 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.casinolovepot.com has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
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):3 complete Content-Type - header (9 urls)
http://casinolovepot.com/wp-admin/setup-config.php


Url with incomplete Content-Type - header - missing charset
http://casinolovepot.com/ 3.33.130.190


Url with incomplete Content-Type - header - missing charset
http://casinolovepot.com/ 15.197.148.33


Url with incomplete Content-Type - header - missing charset
http://www.casinolovepot.com/wp-admin/setup-config.php


Url with incomplete Content-Type - header - missing charset
http://www.casinolovepot.com/ 3.33.130.190


Url with incomplete Content-Type - header - missing charset
http://www.casinolovepot.com/ 15.197.148.33


Url with incomplete Content-Type - header - missing charset
Bhttps://casinolovepot.com/ 34.125.66.187
301

Missing HSTS-Header
Bhttps://www.casinolovepot.com/ 34.125.66.187
301

Missing HSTS-Header
Dhttp://casinolovepot.com/ 34.125.66.187
302
http://casinolovepot.com/wp-admin/setup-config.php
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://www.casinolovepot.com/ 34.125.66.187
302
http://www.casinolovepot.com/wp-admin/setup-config.php
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.
Fhttps://casinolovepot.com/ 34.125.66.187
301
http://casinolovepot.com/
Wrong redirect https - http - never redirect https to http
Fhttps://www.casinolovepot.com/ 34.125.66.187
301
http://www.casinolovepot.com/
Wrong redirect https - http - never redirect https to http
Fhttps://34.125.66.187/ 34.125.66.187
301
http://34.125.66.187/
Wrong redirect https - http - never redirect https to http
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.
Khttp://casinolovepot.com/ 15.197.148.33, Status 200

http://casinolovepot.com/ 34.125.66.187, Status 302
Configuration problem - different ip addresses with different status
Khttp://casinolovepot.com/ 3.33.130.190, Status 200

http://casinolovepot.com/ 34.125.66.187, Status 302
Configuration problem - different ip addresses with different status
Khttp://www.casinolovepot.com/ 15.197.148.33, Status 200

http://www.casinolovepot.com/ 34.125.66.187, Status 302
Configuration problem - different ip addresses with different status
Khttp://www.casinolovepot.com/ 3.33.130.190, Status 200

http://www.casinolovepot.com/ 34.125.66.187, Status 302
Configuration problem - different ip addresses with different status
Khttps://casinolovepot.com/ 15.197.148.33, Status -16

https://casinolovepot.com/ 34.125.66.187, Status 301
Configuration problem - different ip addresses with different status
Khttps://casinolovepot.com/ 3.33.130.190, Status -16

https://casinolovepot.com/ 34.125.66.187, Status 301
Configuration problem - different ip addresses with different status
Khttps://www.casinolovepot.com/ 15.197.148.33, Status -16

https://www.casinolovepot.com/ 34.125.66.187, Status 301
Configuration problem - different ip addresses with different status
Khttps://www.casinolovepot.com/ 3.33.130.190, Status -16

https://www.casinolovepot.com/ 34.125.66.187, Status 301
Configuration problem - different ip addresses with different status
Khttp://casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 15.197.148.33, Status -16

http://casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.125.66.187, Status 200
Configuration problem - different ip addresses with different status
Khttp://casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.33.130.190, Status -16

http://casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.125.66.187, Status 200
Configuration problem - different ip addresses with different status
Khttp://www.casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 15.197.148.33, Status -16

http://www.casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.125.66.187, Status 200
Configuration problem - different ip addresses with different status
Khttp://www.casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.33.130.190, Status -16

http://www.casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.125.66.187, Status 200
Configuration problem - different ip addresses with different status
Nhttps://casinolovepot.com/ 34.125.66.187
301
http://casinolovepot.com/
Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://www.casinolovepot.com/ 34.125.66.187
301
http://www.casinolovepot.com/
Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://34.125.66.187/ 34.125.66.187
301
http://34.125.66.187/
Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain casinolovepot.com, 3 ip addresses, 3 different http results.
Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain www.casinolovepot.com, 3 ip addresses, 3 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.casinolovepot.com

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 29 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 29 Queries complete, 29 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 14.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns63.domaincontrol.com, ns64.domaincontrol.com, 2 Name Servers included in Delegation: ns63.domaincontrol.com, ns64.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns63.domaincontrol.com, ns64.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns63.domaincontrol.com.
AGood: Only one SOA.Primary Name Server found.: ns63.domaincontrol.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns63.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: ns63.domaincontrol.com, ns64.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.69., 97.74.101.
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:2154:, 2603:0005:2254:, 2 different subnets (first four blocks): 2603:0005:2154:0000:, 2603:0005:2254: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
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

Ahttp://casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.125.66.187
200

Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
Ahttp://www.casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.125.66.187
200

Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.33.130.190
-16

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 15.197.148.33
-16

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.33.130.190
-16

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.casinolovepot.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 15.197.148.33
-16

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. 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: 149364 milliseconds, 149.364 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
casinolovepot.com
34.125.66.187
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
casinolovepot.com
34.125.66.187
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Self signed certificate
1CN=www.airdropme.me, OU=IT, O=Hestia Control Panel, L=San Francisco, C=US, ST=California


www.casinolovepot.com
34.125.66.187
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok

www.casinolovepot.com
34.125.66.187
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Self signed certificate
1CN=www.airdropme.me, OU=IT, O=Hestia Control Panel, L=San Francisco, C=US, ST=California


34.125.66.187
34.125.66.187
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok

34.125.66.187
34.125.66.187
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
http/2 via ALPN supported 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Self signed certificate
1CN=www.airdropme.me, OU=IT, O=Hestia Control Panel, L=San Francisco, C=US, ST=California


9. Certificates

1.
1.
CN=www.airdropme.me, OU=IT, O=Hestia Control Panel, L=San Francisco, S=California, C=US
10.06.2024
10.06.2025
expires in 360 days

1.
1.
CN=www.airdropme.me, OU=IT, O=Hestia Control Panel, L=San Francisco, S=California, C=US
10.06.2024

10.06.2025
expires in 360 days


KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:125816AC66C48A9A8D146FCA06EBD3D5CEBEDE39
Thumbprint:46974CA998FDFB3C95BD417A3BBF360CE0572F90
SHA256 / Certificate:P3oWwffvdA7NdBadkeiCpnkmkPur148Nd6d6PLEfU5k=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):911a66a138eed24ae41e1e6589d6096c80ac4d8009f51f05a4db2b4156b45ac8
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:

UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.


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. Nameserver - IP-Adresses

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

QNr.DomainTypeNS used
1
com
NS
g.root-servers.net (2001:500:12::d0d)

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
ns63.domaincontrol.com
NS
l.gtld-servers.net (2001:500:d937::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
ns64.domaincontrol.com
NS
l.gtld-servers.net (2001:500:d937::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
e.gtld-servers.net (2001:502:1ca1::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
6
a11-64.akam.net
NS
e.gtld-servers.net (2001:502:1ca1::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
7
a20-65.akam.net
NS
e.gtld-servers.net (2001:502:1ca1::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
8
a6-66.akam.net
NS
e.gtld-servers.net (2001:502:1ca1::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
9
a8-67.akam.net
NS
e.gtld-servers.net (2001:502:1ca1::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
10
a9-67.akam.net
NS
e.gtld-servers.net (2001:502:1ca1::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
11
a6-67.akam.net
NS
e.gtld-servers.net (2001:502:1ca1::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
12
a1-245.akam.net: 193.108.91.245
A
a1-67.akam.net (2600:1401:2::43)
13
a1-245.akam.net: 2600:1401:2::f5
AAAA
a1-67.akam.net (2600:1401:2::43)
14
a11-64.akam.net: 84.53.139.64
A
a1-67.akam.net (2600:1401:2::43)
15
a11-64.akam.net: 2600:1480:1::40
AAAA
a1-67.akam.net (2600:1401:2::43)
16
a20-65.akam.net: 95.100.175.65
A
a1-67.akam.net (2600:1401:2::43)
17
a20-65.akam.net: 2a02:26f0:67::41
AAAA
a1-67.akam.net (2600:1401:2::43)
18
a6-66.akam.net: 23.211.133.66
A
a1-67.akam.net (2600:1401:2::43)
19
a6-66.akam.net: 2600:1401:1::42
AAAA
a1-67.akam.net (2600:1401:2::43)
20
a8-67.akam.net: 2.16.40.67
A
a1-67.akam.net (2600:1401:2::43)
21
a8-67.akam.net: 2600:1403:a::43
AAAA
a1-67.akam.net (2600:1401:2::43)
22
a9-67.akam.net: 184.85.248.67
A
a1-67.akam.net (2600:1401:2::43)
23
a9-67.akam.net: 2a02:26f0:117::43
AAAA
a1-67.akam.net (2600:1401:2::43)
24
a6-67.akam.net: 23.211.133.67
A
a1-67.akam.net (2600:1401:2::43)
25
a6-67.akam.net: 2600:1401:1::43
AAAA
a1-67.akam.net (2600:1401:2::43)
26
ns63.domaincontrol.com: 97.74.101.42
A
a1-245.akam.net (2600:1401:2::f5)
27
ns63.domaincontrol.com: 2603:5:2154::2a
AAAA
a1-245.akam.net (2600:1401:2::f5)
28
ns64.domaincontrol.com: 173.201.69.42
A
a1-245.akam.net (2600:1401:2::f5)
29
ns64.domaincontrol.com: 2603:5:2254::2a
AAAA
a1-245.akam.net (2600:1401:2::f5)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.casinolovepot.com



1
0
casinolovepot.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
casinolovepot.com

ok
1
0
www.casinolovepot.com


1
0
_acme-challenge.casinolovepot.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.casinolovepot.com

Name Error - The domain name does not exist
1
0
_acme-challenge.casinolovepot.com.casinolovepot.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.casinolovepot.com.casinolovepot.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.casinolovepot.com.www.casinolovepot.com

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites




Skipped, CDN used or too many ip addresses






17. Portchecks

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



Permalink: https://check-your-website.server-daten.de/?i=810cad1f-89b3-48be-bf36-ad06cc9f6c41


Last Result: https://check-your-website.server-daten.de/?q=casinolovepot.com - 2024-06-11 13:45:31


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

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

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