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




N

No trusted Certificate

Checked:
26.05.2023 08:01:26


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
vanes32.ru
A
80.79.123.125
London/England/United Kingdom (GB) - Aktsiaselts WaveCom
No Hostname found
yes
1
0

AAAA

yes


www.vanes32.ru
A
80.79.123.125
London/England/United Kingdom (GB) - Aktsiaselts WaveCom
No Hostname found
yes
1
0

AAAA

yes


*.vanes32.ru
A
80.79.123.125
yes



AAAA

yes



CNAME

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



Public Key with Algorithm 8, KeyTag 60955, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 18274, DigestType 2 and Digest qzXRfT8560LO4UxicyR5ONM+7qqfXKpws4WNv0vT6Hs=



1 RRSIG RR to validate DS RR found



RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 08.06.2023, 05:00:00 +, Signature-Inception: 26.05.2023, 04:00:00 +, KeyTag 60955, Signer-Name: (root)



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



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 59931, Flags 256



Public Key with Algorithm 8, KeyTag 64410, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 11.06.2023, 00:00:00 +, Signature-Inception: 22.05.2023, 00:00:00 +, KeyTag 18274, Signer-Name: ru



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



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

Zone: vanes32.ru
vanes32.ru
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 "fgbqgmkbmh98vqhi1dgdete9pghpft2c" between the hashed NSEC3-owner "fgb9f7qlfm6n96nhj7o30cscjon1hvio" and the hashed NextOwner "fghd0t7poav5ogvkqguas3divt7nravl". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner fgb9f7qlfm6n96nhj7o30cscjon1hvio.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 11.06.2023, 23:17:08 +, Signature-Inception: 10.05.2023, 08:19:18 +, KeyTag 64410, Signer-Name: ru



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "j20c0qkdhua3cumnkst289ff06u2sq91" as Owner. That's the Hash of "ru" with the NextHashedOwnerName "j21c11shootmoeqkprm91c8agl4886m6". So that domain name is the Closest Encloser of "vanes32.ru". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner j20c0qkdhua3cumnkst289ff06u2sq91.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.06.2023, 07:56:14 +, Signature-Inception: 07.05.2023, 12:18:48 +, KeyTag 64410, Signer-Name: ru



0 DNSKEY RR found




Zone: www.vanes32.ru
www.vanes32.ru
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.vanes32.ru
  clint.ns.cloudflare.com / 67m70

vanes32.ru
  clint.ns.cloudflare.com / 67m62
108.162.193.90
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
172.64.33.90
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
173.245.59.90
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
2606:4700:58::adf5:3b5a
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.


 
2803:f800:50::6ca2:c15a
San José/Provincia de San Jose/Costa Rica (CR) - Cloudflare, Inc.


 
2a06:98c1:50::ac40:215a
London/England/United Kingdom (GB) - Cloudflare, Inc.


  georgia.ns.cloudflare.com / 67m48
108.162.194.48
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
162.159.38.48
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
172.64.34.48
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
2606:4700:50::a29f:2630
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.


 
2803:f800:50::6ca2:c230
San José/Provincia de San Jose/Costa Rica (CR) - Cloudflare, Inc.


 
2a06:98c1:50::ac40:2230
London/England/United Kingdom (GB) - Cloudflare, Inc.

ru
  a.dns.ripn.net / tau-m9-ns5.ripn.net


  b.dns.ripn.net / gamma-std.ripn.net


  d.dns.ripn.net / gamma2-nsk.ripn.net


  e.dns.ripn.net / gamma-ekt.ripn.net


  f.dns.ripn.net / gamma-vlv.ripn.net


4. SOA-Entries


Domain:ru
Zone-Name:ru
Primary:a.dns.ripn.net
Mail:hostmaster.ripn.net
Serial:4055864
Refresh:86400
Retry:14400
Expire:2592000
TTL:3600
num Entries:5


Domain:vanes32.ru
Zone-Name:vanes32.ru
Primary:clint.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2310477542
Refresh:10000
Retry:2400
Expire:604800
TTL:1800
num Entries:12


Domain:www.vanes32.ru
Zone-Name:vanes32.ru
Primary:clint.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2310477542
Refresh:10000
Retry:2400
Expire:604800
TTL:1800
num Entries:1


5. Screenshots

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

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://vanes32.ru/
80.79.123.125
-14

10.050
T
Timeout - The operation has timed out

• http://www.vanes32.ru/
80.79.123.125
-14

10.027
T
Timeout - The operation has timed out

• https://vanes32.ru/
80.79.123.125
403

3.303
M
Forbidden
small visible content (num chars: 0)
Date: Fri, 26 May 2023 06:02:38 GMT
Content-Length: 0
Connection: close

• https://www.vanes32.ru/
80.79.123.125
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
2.736
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
small visible content (num chars: 18)
404 page not found
Content-Type: text/plain; charset=utf-8
X-Content-Type-Options: nosniff
Date: Fri, 26 May 2023 06:02:42 GMT
Content-Length: 19
Connection: close

• http://vanes32.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
80.79.123.125
-14

10.067
T
Timeout - The operation has timed out
Visible Content:

• http://www.vanes32.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
80.79.123.125
-14

10.030
T
Timeout - The operation has timed out
Visible Content:

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

Html is minified: 100.00 %
2.710
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
small visible content (num chars: 18)
404 page not found
Content-Type: text/plain; charset=utf-8
X-Content-Type-Options: nosniff
Date: Fri, 26 May 2023 06:03:07 GMT
Content-Length: 19
Connection: close

7. Comments


1. General Results, most used to calculate the result

Aname "vanes32.ru" is domain, public suffix is ".ru", top-level-domain is ".ru", top-level-domain-type is "country-code", Country is Russian Federation (the), tld-manager is "Coordination Center for TLD RU", num .ru-domains preloaded: 2472 (complete: 221801)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: vanes32.ru has only one ip address.
Warning: Only one ip address found: www.vanes32.ru 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: vanes32.ru 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.vanes32.ru has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Bhttps://vanes32.ru/ 80.79.123.125
403

Missing HSTS-Header
Bhttps://www.vanes32.ru/ 80.79.123.125
404

Missing HSTS-Header
CError - no version with Http-Status 200
HFatal error: No https - result with http-status 200, no encryption
Mhttps://vanes32.ru/ 80.79.123.125
403

Misconfiguration - main pages should never send http status 400 - 499
Mhttps://www.vanes32.ru/ 80.79.123.125
404

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

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://www.vanes32.ru/ 80.79.123.125
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://80.79.123.125/ 80.79.123.125
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Ovanes32.ru / 80.79.123.125 / 443


Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 4 Cipher Suites without Forward Secrecy found
Owww.vanes32.ru / 80.79.123.125 / 443


Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 4 Cipher Suites without Forward Secrecy found
XFatal error: Nameserver doesn't support TCP connection: b.dns.ripn.net: Timeout
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.vanes32.ru, 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain vanes32.ru, 1 ip addresses.
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.vanes32.ru

2. Header-Checks

Awww.vanes32.ru 80.79.123.125
X-Content-Type-Options
Ok: Header without syntax errors found: nosniff
Fvanes32.ru 80.79.123.125
Content-Security-Policy
Critical: Missing Header:
Fvanes32.ru 80.79.123.125
X-Content-Type-Options
Critical: Missing Header:
Fvanes32.ru 80.79.123.125
Referrer-Policy
Critical: Missing Header:
Fvanes32.ru 80.79.123.125
Permissions-Policy
Critical: Missing Header:
Fwww.vanes32.ru 80.79.123.125
Content-Security-Policy
Critical: Missing Header:
Fwww.vanes32.ru 80.79.123.125
Referrer-Policy
Critical: Missing Header:
Fwww.vanes32.ru 80.79.123.125
Permissions-Policy
Critical: Missing Header:

3. DNS- and NameServer - Checks

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: clint.ns.cloudflare.com, georgia.ns.cloudflare.com, 2 Name Servers included in Delegation: clint.ns.cloudflare.com, georgia.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: clint.ns.cloudflare.com, georgia.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: clint.ns.cloudflare.com.
AGood: Only one SOA.Primary Name Server found.: clint.ns.cloudflare.com.
AGood: SOA.Primary Name Server included in the delegation set.: clint.ns.cloudflare.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: clint.ns.cloudflare.com, georgia.ns.cloudflare.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
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: cloudflare.com
AGood: Name servers with different Country locations found: 2 Name Servers, 3 Countries: CA, CR, GB
AInfo: Ipv4-Subnet-list: 6 Name Servers, 4 different subnets (first Byte): 108., 162., 172., 173., 4 different subnets (first two Bytes): 108.162., 162.159., 172.64., 173.245., 6 different subnets (first three Bytes): 108.162.193., 108.162.194., 162.159.38., 172.64.33., 172.64.34., 173.245.59.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2606:, 2803:, 2a06:, 3 different subnets (first two blocks): 2606:4700:, 2803:f800:, 2a06:98c1:, 4 different subnets (first three blocks): 2606:4700:0050:, 2606:4700:0058:, 2803:f800:0050:, 2a06:98c1:0050:, 4 different subnets (first four blocks): 2606:4700:0050:0000:, 2606:4700:0058:0000:, 2803:f800:0050:0000:, 2a06:98c1:0050:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 12 good Nameserver
AGood: Nameserver supports Echo Capitalization: 12 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 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

http://vanes32.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 80.79.123.125
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. 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.vanes32.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 80.79.123.125
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. 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
https://www.vanes32.ru/ 80.79.123.125
404
2.736 seconds
Warning: 404 needs more then one second
https://80.79.123.125/ 80.79.123.125
404
2.710 seconds
Warning: 404 needs more then one second
ADuration: 279987 milliseconds, 279.987 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
vanes32.ru
80.79.123.125
443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
vanes32.ru
80.79.123.125
443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
http/2 via ALPN supported 
SNI required
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
SNI required
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=vanes32.ru

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

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


www.vanes32.ru
80.79.123.125
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok

www.vanes32.ru
80.79.123.125
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=TRAEFIK DEFAULT CERT


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

80.79.123.125
80.79.123.125
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=TRAEFIK DEFAULT CERT


9. Certificates

1.
1.
CN=vanes32.ru
23.04.2023
22.07.2023
271 days expired
vanes32.ru - 1 entry
1.
1.
CN=vanes32.ru
23.04.2023

22.07.2023
271 days expired
vanes32.ru - 1 entry

KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0428A0938A28C8F525A68ECF3EEF89E1A518
Thumbprint:CC5C5C76EC9B51B1660C098800870ADEF0777229
SHA256 / Certificate:Qd6+Nu2+fJOnt1LK34802E6aGjV0yMMzsrnjLbflcbc=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):25ee476ae20a0170b126d0839034e1b43695e35e4647b106a364ad86c748eecd
SHA256 hex / Subject Public Key Information (SPKI):25ee476ae20a0170b126d0839034e1b43695e35e4647b106a364ad86c748eecd (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 515 days


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

15.09.2025
expires in 515 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 4064 days


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

04.06.2035
expires in 4064 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:


2.
1.
CN=TRAEFIK DEFAULT CERT
26.05.2023
25.05.2024
expires in 37 days
d630ea4a7eccbe76dc74509b3e79fa6f.5f2370f82a874b6cbc9c817b1e163bcb.traefik.default - 1 entry
2.
1.
CN=TRAEFIK DEFAULT CERT
26.05.2023

25.05.2024
expires in 37 days
d630ea4a7eccbe76dc74509b3e79fa6f.5f2370f82a874b6cbc9c817b1e163bcb.traefik.default - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:44C1B3144E6507CD560B11F4BFBD75B9
Thumbprint:7E0B5FB584BBD32BD750738EC04DFB04AFBDA7B1
SHA256 / Certificate:+ygzorZeZdIwGTeMUGsRe8AalPnFiul53a49WfP3cWg=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):b4cdc1d09ef24aa7ba89d79615b62a53d8d133e8d26fe6fa71bdea825044f81c
SHA256 hex / Subject Public Key Information (SPKI):b4cdc1d09ef24aa7ba89d79615b62a53d8d133e8d26fe6fa71bdea825044f81c (is buggy, ignore the result)
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:Serverauthentifizierung (1.3.6.1.5.5.7.3.1)

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)

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0
0
14
CN=GTS CA 1P5, O=Google Trust Services LLC, C=US
0
0
1
CN=GTS CA 2P2, O=Google Trust Services LLC, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
5223603404
precert
CN=GTS CA 2P2, O=Google Trust Services LLC, C=US
2023-05-13 15:56:26
2023-08-11 15:56:25
*.vanes32.ru, vanes32.ru - 2 entries


5140817218
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-04-26 06:04:27
2023-07-25 06:04:26
vanes32.ru - 1 entries


5128834924
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-04-23 15:43:03
2023-07-22 15:43:02
vanes32.ru - 1 entries


5127413915
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-04-23 06:27:12
2023-07-22 06:27:11
vanes32.ru - 1 entries


5124372429
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-04-22 13:28:30
2023-07-21 13:28:29
vanes32.ru - 1 entries


5124368267
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-04-22 13:28:30
2023-07-21 13:28:29
www.vanes32.ru - 1 entries


5109968591
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-04-19 05:57:10
2023-07-18 05:57:09
vanes32.ru - 1 entries


5109968184
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-04-19 05:57:01
2023-07-18 05:57:00
www.vanes32.ru - 1 entries


5105536266
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-04-18 08:42:57
2023-07-17 08:42:56
vanes32.ru - 1 entries


4949217980
precert
CN=GTS CA 1P5, O=Google Trust Services LLC, C=US
2023-03-15 12:32:13
2023-06-13 12:32:12
*.vanes32.ru, vanes32.ru - 2 entries


4939092079
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-03-13 05:19:28
2023-06-11 05:19:27
www.vanes32.ru - 1 entries


4933111890
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-03-11 17:23:56
2023-06-09 17:23:55
vanes32.ru - 1 entries


4929674283
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-03-10 21:24:44
2023-06-08 21:24:43
vanes32.ru - 1 entries


4929292790
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-03-10 18:59:50
2023-06-08 18:59:49
www.vanes32.ru - 1 entries


4928913453
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-03-10 16:41:59
2023-06-08 16:41:58
vanes32.ru - 1 entries


4926984112
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-03-10 05:36:48
2023-06-08 05:36:47
vanes32.ru - 1 entries



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

Small Code Update - wait one minute


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: clint.ns.cloudflare.com, georgia.ns.cloudflare.com

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

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

Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com

Answer: ns3.cloudflare.com
162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2

Answer: ns4.cloudflare.com
162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837

Answer: ns5.cloudflare.com
162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937

Answer: ns6.cloudflare.com
162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506

Answer: ns7.cloudflare.com
162.159.4.8
3
georgia.ns.cloudflare.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com

Answer: ns3.cloudflare.com
162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2

Answer: ns4.cloudflare.com
162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837

Answer: ns5.cloudflare.com
162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937

Answer: ns6.cloudflare.com
162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506

Answer: ns7.cloudflare.com
162.159.4.8
4
clint.ns.cloudflare.com: 108.162.193.90, 172.64.33.90, 173.245.59.90
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
5
clint.ns.cloudflare.com: 2606:4700:58::adf5:3b5a, 2803:f800:50::6ca2:c15a, 2a06:98c1:50::ac40:215a
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
6
georgia.ns.cloudflare.com: 108.162.194.48, 162.159.38.48, 172.64.34.48
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
7
georgia.ns.cloudflare.com: 2606:4700:50::a29f:2630, 2803:f800:50::6ca2:c230, 2a06:98c1:50::ac40:2230
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.vanes32.ru
0

no CAA entry found
1
0
vanes32.ru
0

no CAA entry found
1
0
ru
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
vanes32.ru

ok
1
0
www.vanes32.ru

ok
1
0
_acme-challenge.vanes32.ru

missing entry or wrong length
1
0
_acme-challenge.www.vanes32.ru

missing entry or wrong length
1
0
_acme-challenge.vanes32.ru.vanes32.ru

perhaps wrong
1
0
_acme-challenge.www.vanes32.ru.vanes32.ru

perhaps wrong
1
0
_acme-challenge.www.vanes32.ru.www.vanes32.ru

perhaps wrong
1
0


15. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
_dmarc
TXT
_dmarc.vanes32.ru

00ok



16. Cipher Suites

DomainIPPortCipher (OpenSsl / IANA)
vanes32.ru
80.79.123.125
443
ECDHE-RSA-CHACHA20-POLY1305
(Secure)
TLSv1.2
0xCC,0xA8
FS
9 Ciphers, 65.15 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



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

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
ECDH
RSA
AESGCM(128)
AEAD



AES256-GCM-SHA384
(Weak)
TLSv1.2
0x00,0x9D
No FS

TLS_RSA_WITH_AES_256_GCM_SHA384
RSA
RSA
AESGCM(256)
AEAD



AES128-GCM-SHA256
(Weak)
TLSv1.2
0x00,0x9C
No FS

TLS_RSA_WITH_AES_128_GCM_SHA256
RSA
RSA
AESGCM(128)
AEAD



ECDHE-RSA-AES256-SHA
(Weak)
TLSv1
0xC0,0x14
FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
ECDH
RSA
AES(256)
SHA1



ECDHE-RSA-AES128-SHA
(Weak)
TLSv1
0xC0,0x13
FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
ECDH
RSA
AES(128)
SHA1



AES256-SHA
(Weak)
SSLv3
0x00,0x35
No FS

TLS_RSA_WITH_AES_256_CBC_SHA
RSA
RSA
AES(256)
SHA1



AES128-SHA
(Weak)
SSLv3
0x00,0x2F
No FS

TLS_RSA_WITH_AES_128_CBC_SHA
RSA
RSA
AES(128)
SHA1
www.vanes32.ru
80.79.123.125
443
ECDHE-RSA-CHACHA20-POLY1305
(Secure)
TLSv1.2
0xCC,0xA8
FS
9 Ciphers, 64.82 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



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

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
ECDH
RSA
AESGCM(128)
AEAD



AES256-GCM-SHA384
(Weak)
TLSv1.2
0x00,0x9D
No FS

TLS_RSA_WITH_AES_256_GCM_SHA384
RSA
RSA
AESGCM(256)
AEAD



AES128-GCM-SHA256
(Weak)
TLSv1.2
0x00,0x9C
No FS

TLS_RSA_WITH_AES_128_GCM_SHA256
RSA
RSA
AESGCM(128)
AEAD



ECDHE-RSA-AES256-SHA
(Weak)
TLSv1
0xC0,0x14
FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
ECDH
RSA
AES(256)
SHA1



ECDHE-RSA-AES128-SHA
(Weak)
TLSv1
0xC0,0x13
FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
ECDH
RSA
AES(128)
SHA1



AES256-SHA
(Weak)
SSLv3
0x00,0x35
No FS

TLS_RSA_WITH_AES_256_CBC_SHA
RSA
RSA
AES(256)
SHA1



AES128-SHA
(Weak)
SSLv3
0x00,0x2F
No FS

TLS_RSA_WITH_AES_128_CBC_SHA
RSA
RSA
AES(128)
SHA1


17. Portchecks

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



Permalink: https://check-your-website.server-daten.de/?i=075c707c-8daa-4b74-9a57-1d62708eb1a6


Last Result: https://check-your-website.server-daten.de/?q=vanes32.ru - 2023-05-26 08:01:26


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

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

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