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



T

Timeout

Checked:
14.01.2022 20:09:31


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
bitwarden.samsepi0l.ovh
A
104.21.58.16
Newark/New Jersey/United States (US) - Cloudflare, Inc.
No Hostname found
yes
1
0

A
172.67.197.52
Newark/New Jersey/United States (US) - Cloudflare, Inc.
No Hostname found
yes
1
0

AAAA
2606:4700:3031::ac43:c534
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.

yes



AAAA
2606:4700:3034::6815:3a10
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.

yes


www.bitwarden.samsepi0l.ovh

Name Error
yes
1
0
*.samsepi0l.ovh
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.bitwarden.samsepi0l.ovh
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 9799, 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.02.2022, 00:00:00 +, Signature-Inception: 11.01.2022, 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: ovh
ovh
1 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 4719, DigestType 2 and Digest UPVql+A90Jd+Jj4bAunA0s+xxNCf08lmV2aJI+EgQHo=



1 RRSIG RR to validate DS RR found



RRSIG-Owner ovh., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.01.2022, 17:00:00 +, Signature-Inception: 14.01.2022, 16:00:00 +, KeyTag 9799, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 13, KeyTag 54275, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ovh., Algorithm: 13, 1 Labels, original TTL: 172800 sec, Signature-expiration: 02.02.2022, 00:01:40 +, Signature-Inception: 14.01.2022, 18:00:11 +, KeyTag 4719, Signer-Name: ovh



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



Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 4719, DigestType 2 and Digest "UPVql+A90Jd+Jj4bAunA0s+xxNCf08lmV2aJI+EgQHo=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: samsepi0l.ovh
samsepi0l.ovh
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 "p85v6i03lk2uk8gqqn37nllbk200c4q2" between the hashed NSEC3-owner "p850nla6p5jm77ajflrn9s7048t56mbi" and the hashed NextOwner "p86f9rgtdq8mmevgchqf93kq9g77kkuo". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner p850nla6p5jm77ajflrn9s7048t56mbi.ovh., Algorithm: 13, 2 Labels, original TTL: 5400 sec, Signature-expiration: 12.02.2022, 04:43:51 +, Signature-Inception: 30.11.2021, 10:20:11 +, KeyTag 54275, Signer-Name: ovh



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ivap9gaoa14gj84009e5eglsk5igjb3i" as Owner. That's the Hash of "ovh" with the NextHashedOwnerName "ivbk2392dh1r13583mkv3nenk6bgkr0m". So that domain name is the Closest Encloser of "samsepi0l.ovh". Opt-Out: True.
Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ivap9gaoa14gj84009e5eglsk5igjb3i.ovh., Algorithm: 13, 2 Labels, original TTL: 5400 sec, Signature-expiration: 16.03.2022, 16:18:08 +, Signature-Inception: 01.01.2022, 23:00:11 +, KeyTag 54275, Signer-Name: ovh



2 DNSKEY RR found



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



Public Key with Algorithm 13, KeyTag 34505, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner samsepi0l.ovh., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 15.03.2022, 18:54:56 +, Signature-Inception: 13.01.2022, 18:54:56 +, KeyTag 2371, Signer-Name: samsepi0l.ovh



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



Error: DNSKEY 2371 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.

Zone: bitwarden.samsepi0l.ovh
bitwarden.samsepi0l.ovh
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "bitwarden.samsepi0l.ovh" and the NextOwner "\000.bitwarden.samsepi0l.ovh". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI, CAA



0 DNSKEY RR found






RRSIG Type 1 validates the A - Result: 104.21.58.16 172.67.197.52
Validated: RRSIG-Owner bitwarden.samsepi0l.ovh., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 15.01.2022, 20:09:46 +, Signature-Inception: 13.01.2022, 18:09:46 +, KeyTag 34505, Signer-Name: samsepi0l.ovh



RRSIG Type 28 validates the AAAA - Result: 2606:4700:3031:0000:0000:0000:AC43:C534 2606:4700:3034:0000:0000:0000:6815:3A10
Validated: RRSIG-Owner bitwarden.samsepi0l.ovh., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 15.01.2022, 20:09:46 +, Signature-Inception: 13.01.2022, 18:09:46 +, KeyTag 34505, Signer-Name: samsepi0l.ovh



CNAME-Query sends a valid NSEC RR as result with the query name "bitwarden.samsepi0l.ovh" equal the NSEC-owner "bitwarden.samsepi0l.ovh" and the NextOwner "\000.bitwarden.samsepi0l.ovh". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner bitwarden.samsepi0l.ovh., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 15.01.2022, 20:09:46 +, Signature-Inception: 13.01.2022, 18:09:46 +, KeyTag 34505, Signer-Name: samsepi0l.ovh



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC RR as result with the query name "bitwarden.samsepi0l.ovh" equal the NSEC-owner "bitwarden.samsepi0l.ovh" and the NextOwner "\000.bitwarden.samsepi0l.ovh". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, 13, MX, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner bitwarden.samsepi0l.ovh., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 15.01.2022, 20:09:46 +, Signature-Inception: 13.01.2022, 18:09:46 +, KeyTag 34505, Signer-Name: samsepi0l.ovh



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.bitwarden.samsepi0l.ovh) sends a valid NSEC RR as result with the query name "_443._tcp.bitwarden.samsepi0l.ovh" equal the NSEC-owner "_443._tcp.bitwarden.samsepi0l.ovh" and the NextOwner "\000._443._tcp.bitwarden.samsepi0l.ovh". So the zone confirmes the not-existence of that TLSA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: RRSIG, NSEC Validated: RRSIG-Owner _443._tcp.bitwarden.samsepi0l.ovh., Algorithm: 13, 5 Labels, original TTL: 3600 sec, Signature-expiration: 15.01.2022, 20:09:46 +, Signature-Inception: 13.01.2022, 18:09:46 +, KeyTag 34505, Signer-Name: samsepi0l.ovh



Status: Good. NoData-Proof required and found.



CAA-Query sends a valid NSEC RR as result with the query name "bitwarden.samsepi0l.ovh" equal the NSEC-owner "bitwarden.samsepi0l.ovh" and the NextOwner "\000.bitwarden.samsepi0l.ovh". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI Validated: RRSIG-Owner bitwarden.samsepi0l.ovh., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 15.01.2022, 20:09:46 +, Signature-Inception: 13.01.2022, 18:09:46 +, KeyTag 34505, Signer-Name: samsepi0l.ovh



Status: Good. NoData-Proof required and found.

Zone: www.bitwarden.samsepi0l.ovh
www.bitwarden.samsepi0l.ovh
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "www.bitwarden.samsepi0l.ovh" and the NextOwner "\000.www.bitwarden.samsepi0l.ovh". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: RRSIG, NSEC


3. Name Servers

DomainNameserverNS-IP
www.bitwarden.samsepi0l.ovh
  curt.ns.cloudflare.com

bitwarden.samsepi0l.ovh
  curt.ns.cloudflare.com / 67m34
108.162.193.94
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


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


 
173.245.59.94
Newark/New Jersey/United States (US) - Cloudflare, Inc.


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


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


 
2a06:98c1:50::ac40:215e
London/England/United Kingdom (GB) - CloudFLARENET-EU

samsepi0l.ovh
  curt.ns.cloudflare.com / 67m34
108.162.193.94
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


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


 
173.245.59.94
Newark/New Jersey/United States (US) - Cloudflare, Inc.


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


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


 
2a06:98c1:50::ac40:215e
London/England/United Kingdom (GB) - CloudFLARENET-EU


  oaklyn.ns.cloudflare.com / 67m60
108.162.194.90
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


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


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


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


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


 
2a06:98c1:50::ac40:225a
London/England/United Kingdom (GB) - CloudFLARENET-EU

ovh
  d.nic.fr


  f.ext.nic.fr


  g.ext.nic.fr


4. SOA-Entries


Domain:ovh
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:3


Domain:samsepi0l.ovh
Zone-Name:samsepi0l.ovh
Primary:curt.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2267672630
Refresh:10000
Retry:2400
Expire:604800
TTL:3600
num Entries:12


Domain:bitwarden.samsepi0l.ovh
Zone-Name:samsepi0l.ovh
Primary:curt.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2267672630
Refresh:10000
Retry:2400
Expire:604800
TTL:3600
num Entries:6


Domain:www.bitwarden.samsepi0l.ovh
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


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://bitwarden.samsepi0l.ovh/
104.21.58.16
-14

10.047
T
Timeout - The operation has timed out

• http://bitwarden.samsepi0l.ovh/
172.67.197.52
-14

10.030
T
Timeout - The operation has timed out

• http://bitwarden.samsepi0l.ovh/
2606:4700:3031::ac43:c534
-14

10.046
T
Timeout - The operation has timed out

• http://bitwarden.samsepi0l.ovh/
2606:4700:3034::6815:3a10
-14

10.047
T
Timeout - The operation has timed out

• https://bitwarden.samsepi0l.ovh/
104.21.58.16
-14

12.246
T
Timeout - The operation has timed out

• https://bitwarden.samsepi0l.ovh/
172.67.197.52
-14

12.167
T
Timeout - The operation has timed out

• https://bitwarden.samsepi0l.ovh/
2606:4700:3031::ac43:c534
-14

12.310
T
Timeout - The operation has timed out

• https://bitwarden.samsepi0l.ovh/
2606:4700:3034::6815:3a10
-14

12.233
T
Timeout - The operation has timed out

• http://bitwarden.samsepi0l.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
104.21.58.16
-14

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

• http://bitwarden.samsepi0l.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
172.67.197.52
-14

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

• http://bitwarden.samsepi0l.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2606:4700:3031::ac43:c534
-14

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

• http://bitwarden.samsepi0l.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2606:4700:3034::6815:3a10
-14

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

• https://104.21.58.16/
104.21.58.16
-10

0.046
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• https://172.67.197.52/
172.67.197.52
-10

0.047
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• https://[2606:4700:3031:0000:0000:0000:ac43:c534]/
2606:4700:3031::ac43:c534
-10

0.077
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• https://[2606:4700:3034:0000:0000:0000:6815:3a10]/
2606:4700:3034::6815:3a10
-10

0.063
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

7. Comments


1. General Results, most used to calculate the result

Aname "bitwarden.samsepi0l.ovh" is subdomain, public suffix is ".ovh", top-level-domain is ".ovh", top-level-domain-type is "generic", tld-manager is "OVH SAS", num .ovh-domains preloaded: 177 (complete: 175327)
Agood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: bitwarden.samsepi0l.ovh has 4 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: bitwarden.samsepi0l.ovh has 2 ipv4, 2 ipv6 addresses
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Phttps://104.21.58.16/ 104.21.58.16
-10

Error creating a TLS-Connection: No more details available.
Phttps://172.67.197.52/ 172.67.197.52
-10

Error creating a TLS-Connection: No more details available.
Phttps://[2606:4700:3031:0000:0000:0000:ac43:c534]/ 2606:4700:3031::ac43:c534
-10

Error creating a TLS-Connection: No more details available.
Phttps://[2606:4700:3034:0000:0000:0000:6815:3a10]/ 2606:4700:3034::6815:3a10
-10

Error creating a TLS-Connection: No more details available.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain bitwarden.samsepi0l.ovh, 4 ip addresses.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain bitwarden.samsepi0l.ovh, 4 ip addresses.

2. 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: curt.ns.cloudflare.com, oaklyn.ns.cloudflare.com, 2 Name Servers included in Delegation: curt.ns.cloudflare.com, oaklyn.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: curt.ns.cloudflare.com, oaklyn.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: curt.ns.cloudflare.com.
AGood: Only one SOA.Primary Name Server found.: curt.ns.cloudflare.com.
AGood: SOA.Primary Name Server included in the delegation set.: curt.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: curt.ns.cloudflare.com, oaklyn.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, 4 Countries: CA, CR, GB, US
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: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: curt.ns.cloudflare.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.
Nameserver doesn't pass all EDNS-Checks: d.nic.fr: 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.
Nameserver doesn't pass all EDNS-Checks: f.ext.nic.fr: 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.
Nameserver doesn't pass all EDNS-Checks: g.ext.nic.fr: 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.

3. Content- and Performance-critical Checks

http://bitwarden.samsepi0l.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.21.58.16
-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://bitwarden.samsepi0l.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.67.197.52
-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://bitwarden.samsepi0l.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3031::ac43:c534
-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://bitwarden.samsepi0l.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3034::6815:3a10
-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
ADuration: 307930 milliseconds, 307.930 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
bitwarden.samsepi0l.ovh
104.21.58.16
443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
bitwarden.samsepi0l.ovh
104.21.58.16
443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
Tls.1.2
Tls.1.1
Tls.1.0


bitwarden.samsepi0l.ovh
172.67.197.52
443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok

bitwarden.samsepi0l.ovh
172.67.197.52
443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
Tls.1.2
Tls.1.1
Tls.1.0


bitwarden.samsepi0l.ovh
2606:4700:3031::ac43:c534
443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok

bitwarden.samsepi0l.ovh
2606:4700:3031::ac43:c534
443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
Tls.1.2
Tls.1.1
Tls.1.0


bitwarden.samsepi0l.ovh
2606:4700:3034::6815:3a10
443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok

bitwarden.samsepi0l.ovh
2606:4700:3034::6815:3a10
443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
Tls.1.2
Tls.1.1
Tls.1.0


bitwarden.samsepi0l.ovh
bitwarden.samsepi0l.ovh
2083
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok

bitwarden.samsepi0l.ovh
bitwarden.samsepi0l.ovh
2083
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
Tls.1.2
Tls.1.1
Tls.1.0


bitwarden.samsepi0l.ovh
bitwarden.samsepi0l.ovh
2087
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok

bitwarden.samsepi0l.ovh
bitwarden.samsepi0l.ovh
2087
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
Tls.1.2
Tls.1.1
Tls.1.0


bitwarden.samsepi0l.ovh
bitwarden.samsepi0l.ovh
2096
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok

bitwarden.samsepi0l.ovh
bitwarden.samsepi0l.ovh
2096
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
Tls.1.2
Tls.1.1
Tls.1.0


bitwarden.samsepi0l.ovh
bitwarden.samsepi0l.ovh
8443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok

bitwarden.samsepi0l.ovh
bitwarden.samsepi0l.ovh
8443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
Tls.1.2
Tls.1.1
Tls.1.0


9. Certificates

1.
1.
CN=sni.cloudflaressl.com, O="Cloudflare, Inc.", L=San Francisco, S=California, C=US
14.01.2022
14.01.2023
expires in 355 days
sni.cloudflaressl.com, samsepi0l.ovh, *.samsepi0l.ovh - 3 entries
1.
1.
CN=sni.cloudflaressl.com, O="Cloudflare, Inc.", L=San Francisco, S=California, C=US
14.01.2022

14.01.2023
expires in 355 days
sni.cloudflaressl.com, samsepi0l.ovh, *.samsepi0l.ovh - 3 entries

KeyalgorithmEC Public Key (256 bit, prime256v1)
Signatur:ECDSA SHA256
Serial Number:0E285453E54B2868C90FC3465A33D2E5
Thumbprint:6AA778A8F238191A129D44F592FE25E2F8118007
SHA256 / Certificate:tRHGc6cbH5tBZTLQj9jualisYI9QE7ySOcHQZG7g0jw=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):94e2637c5388640351ae9f5fbc012627b2307900e7a209274d48f44328530540
SHA256 hex / Subject Public Key Information (SPKI):94e2637c5388640351ae9f5fbc012627b2307900e7a209274d48f44328530540 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.com
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=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
27.01.2020
01.01.2025
expires in 1073 days


2.
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
27.01.2020

01.01.2025
expires in 1073 days


KeyalgorithmEC Public Key (256 bit, prime256v1)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A3787645E5FB48C224EFD1BED140C3C
Thumbprint:B3DD7606D2B5A8B4A13771DBECC9EE1CECAFA38A
SHA256 / Certificate:OrvmPa91bFAWtrhfUgFf2Oisvid8UIexJ6YFY6hB7Yo=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):144cd5394a78745de02346553d126115b48955747eb9098c1fae7186cd60947e
SHA256 hex / Subject Public Key Information (SPKI):144cd5394a78745de02346553d126115b48955747eb9098c1fae7186cd60947e
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)


3.
CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE
12.05.2000
13.05.2025
expires in 1205 days


3.
CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE
12.05.2000

13.05.2025
expires in 1205 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:020000B9
Thumbprint:D4DE20D05E66FC53FE1A50882C78DB2852CAE474
SHA256 / Certificate:Fq9XqfZ2sKsSYJWqXrre8iqzERnWRKyVzUuT2/Pyaus=
SHA256 hex / Cert (DANE * 0 1):16af57a9f676b0ab126095aa5ebadef22ab31119d644ac95cd4b93dbf3f26aeb
SHA256 hex / PublicKey (DANE * 1 1):63d9af9b47b1064d49a10e7b7fd566dbc8caa399459bfc2829c571ad8c6ef34a
SHA256 hex / Subject Public Key Information (SPKI):63d9af9b47b1064d49a10e7b7fd566dbc8caa399459bfc2829c571ad8c6ef34a
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" > 2019 are listed

Issuerlast 7 daysactivenum Certs
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
0
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
5977141959
precert
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
2022-01-13 23:00:00
2023-01-13 22:59:59
*.samsepi0l.ovh, samsepi0l.ovh, sni.cloudflaressl.com
3 entries



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: curt.ns.cloudflare.com, oaklyn.ns.cloudflare.com

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

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
curt.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
oaklyn.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
curt.ns.cloudflare.com: 108.162.193.94, 172.64.33.94, 173.245.59.94
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
5
curt.ns.cloudflare.com: 2606:4700:58::adf5:3b5e, 2803:f800:50::6ca2:c15e, 2a06:98c1:50::ac40:215e
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
6
oaklyn.ns.cloudflare.com: 108.162.194.90, 162.159.38.90, 172.64.34.90
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
7
oaklyn.ns.cloudflare.com: 2606:4700:50::a29f:265a, 2803:f800:50::6ca2:c25a, 2a06:98c1:50::ac40:225a
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
bitwarden.samsepi0l.ovh
0

no CAA entry found
1
0
samsepi0l.ovh
0

no CAA entry found
1
0
ovh
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
samsepi0l.ovh
1|www.samsepi0l.ovh
ok
1
0
bitwarden.samsepi0l.ovh

ok
1
0
_acme-challenge.bitwarden.samsepi0l.ovh

Name Error - The domain name does not exist
1
0
_acme-challenge.bitwarden.samsepi0l.ovh.samsepi0l.ovh

Name Error - The domain name does not exist
1
0
_acme-challenge.bitwarden.samsepi0l.ovh.bitwarden.samsepi0l.ovh

Name Error - The domain name does not exist
1
0


15. Portchecks

Domain or IPPortDescriptionResultAnswer
bitwarden.samsepi0l.ovh
21
FTP



bitwarden.samsepi0l.ovh
21
FTP



bitwarden.samsepi0l.ovh
22
SSH



bitwarden.samsepi0l.ovh
22
SSH



bitwarden.samsepi0l.ovh
25
SMTP



bitwarden.samsepi0l.ovh
25
SMTP



bitwarden.samsepi0l.ovh
53
DNS



bitwarden.samsepi0l.ovh
53
DNS



bitwarden.samsepi0l.ovh
110
POP3



bitwarden.samsepi0l.ovh
110
POP3



bitwarden.samsepi0l.ovh
143
IMAP



bitwarden.samsepi0l.ovh
143
IMAP



bitwarden.samsepi0l.ovh
465
SMTP (encrypted)



bitwarden.samsepi0l.ovh
465
SMTP (encrypted)



bitwarden.samsepi0l.ovh
587
SMTP (encrypted, submission)



bitwarden.samsepi0l.ovh
587
SMTP (encrypted, submission)



bitwarden.samsepi0l.ovh
993
IMAP (encrypted)



bitwarden.samsepi0l.ovh
993
IMAP (encrypted)



bitwarden.samsepi0l.ovh
995
POP3 (encrypted)



bitwarden.samsepi0l.ovh
995
POP3 (encrypted)



bitwarden.samsepi0l.ovh
1433
MS SQL



bitwarden.samsepi0l.ovh
1433
MS SQL



bitwarden.samsepi0l.ovh
2082
cPanel (http)
open
http://bitwarden.samsepi0l.ovh:2082/
Http-Status: -14
Timeout - The operation has timed out

bitwarden.samsepi0l.ovh
2082
cPanel (http)
open
http://bitwarden.samsepi0l.ovh:2082/
Http-Status: -14
Timeout - The operation has timed out

bitwarden.samsepi0l.ovh
2083
cPanel (https)
open
https://bitwarden.samsepi0l.ovh:2083/
Http-Status: -14
Timeout - The operation has timed out
Certificate is valid
bitwarden.samsepi0l.ovh
2083
cPanel (https)
open
https://bitwarden.samsepi0l.ovh:2083/
Http-Status: -14
Timeout - The operation has timed out
Certificate is valid
bitwarden.samsepi0l.ovh
2086
WHM (http)
open
http://bitwarden.samsepi0l.ovh:2086/
Http-Status: -14
Timeout - The operation has timed out

bitwarden.samsepi0l.ovh
2086
WHM (http)
open
http://bitwarden.samsepi0l.ovh:2086/
Http-Status: -14
Timeout - The operation has timed out

bitwarden.samsepi0l.ovh
2087
WHM (https)
open
https://bitwarden.samsepi0l.ovh:2087/
Http-Status: -14
Timeout - The operation has timed out
Certificate is valid
bitwarden.samsepi0l.ovh
2087
WHM (https)
open
https://bitwarden.samsepi0l.ovh:2087/
Http-Status: -14
Timeout - The operation has timed out
Certificate is valid
bitwarden.samsepi0l.ovh
2089
cPanel Licensing



bitwarden.samsepi0l.ovh
2089
cPanel Licensing



bitwarden.samsepi0l.ovh
2095
cPanel Webmail (http)
open
http://bitwarden.samsepi0l.ovh:2095/
Http-Status: -14
Timeout - The operation has timed out

bitwarden.samsepi0l.ovh
2095
cPanel Webmail (http)
open
http://bitwarden.samsepi0l.ovh:2095/
Http-Status: -14
Timeout - The operation has timed out

bitwarden.samsepi0l.ovh
2096
cPanel Webmail (https)
open
https://bitwarden.samsepi0l.ovh:2096/
Http-Status: -14
Timeout - The operation has timed out
Certificate is valid
bitwarden.samsepi0l.ovh
2096
cPanel Webmail (https)
open
https://bitwarden.samsepi0l.ovh:2096/
Http-Status: -14
Timeout - The operation has timed out
Certificate is valid
bitwarden.samsepi0l.ovh
2222
DirectAdmin (http)



bitwarden.samsepi0l.ovh
2222
DirectAdmin (http)



bitwarden.samsepi0l.ovh
2222
DirectAdmin (https)



bitwarden.samsepi0l.ovh
2222
DirectAdmin (https)



bitwarden.samsepi0l.ovh
3306
mySql



bitwarden.samsepi0l.ovh
3306
mySql



bitwarden.samsepi0l.ovh
5224
Plesk Licensing



bitwarden.samsepi0l.ovh
5224
Plesk Licensing



bitwarden.samsepi0l.ovh
5432
PostgreSQL



bitwarden.samsepi0l.ovh
5432
PostgreSQL



bitwarden.samsepi0l.ovh
8080
Ookla Speedtest (http)
open
http://bitwarden.samsepi0l.ovh:8080/
Http-Status: -14
Timeout - The operation has timed out

bitwarden.samsepi0l.ovh
8080
Ookla Speedtest (http)
open
http://bitwarden.samsepi0l.ovh:8080/
Http-Status: -14
Timeout - The operation has timed out

bitwarden.samsepi0l.ovh
8080
Ookla Speedtest (https)
open
https://bitwarden.samsepi0l.ovh:8080/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

bitwarden.samsepi0l.ovh
8080
Ookla Speedtest (https)
open
https://bitwarden.samsepi0l.ovh:8080/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

bitwarden.samsepi0l.ovh
8083
VestaCP http



bitwarden.samsepi0l.ovh
8083
VestaCP http



bitwarden.samsepi0l.ovh
8083
VestaCP https



bitwarden.samsepi0l.ovh
8083
VestaCP https



bitwarden.samsepi0l.ovh
8443
Plesk Administration (https)
open
https://bitwarden.samsepi0l.ovh:8443/
Http-Status: -14
Timeout - The operation has timed out
Certificate is valid
bitwarden.samsepi0l.ovh
8443
Plesk Administration (https)
open
https://bitwarden.samsepi0l.ovh:8443/
Http-Status: -14
Timeout - The operation has timed out
Certificate is valid
bitwarden.samsepi0l.ovh
8447
Plesk Installer + Updates



bitwarden.samsepi0l.ovh
8447
Plesk Installer + Updates



bitwarden.samsepi0l.ovh
8880
Plesk Administration (http)
open
http://bitwarden.samsepi0l.ovh:8880/
Http-Status: -14
Timeout - The operation has timed out

bitwarden.samsepi0l.ovh
8880
Plesk Administration (http)
open
http://bitwarden.samsepi0l.ovh:8880/
Http-Status: -14
Timeout - The operation has timed out

bitwarden.samsepi0l.ovh
10000
Webmin (http)



bitwarden.samsepi0l.ovh
10000
Webmin (http)



bitwarden.samsepi0l.ovh
10000
Webmin (https)



bitwarden.samsepi0l.ovh
10000
Webmin (https)



104.21.58.16
21
FTP



104.21.58.16
21
FTP



104.21.58.16
22
SSH



104.21.58.16
22
SSH



104.21.58.16
25
SMTP



104.21.58.16
25
SMTP



104.21.58.16
53
DNS



104.21.58.16
53
DNS



104.21.58.16
110
POP3



104.21.58.16
110
POP3



104.21.58.16
143
IMAP



104.21.58.16
143
IMAP



104.21.58.16
465
SMTP (encrypted)



104.21.58.16
465
SMTP (encrypted)



104.21.58.16
587
SMTP (encrypted, submission)



104.21.58.16
587
SMTP (encrypted, submission)



104.21.58.16
993
IMAP (encrypted)



104.21.58.16
993
IMAP (encrypted)



104.21.58.16
995
POP3 (encrypted)



104.21.58.16
995
POP3 (encrypted)



104.21.58.16
1433
MS SQL



104.21.58.16
1433
MS SQL



104.21.58.16
2082
cPanel (http)
open
http://104.21.58.16:2082/
Http-Status: 403
Forbidden

104.21.58.16
2082
cPanel (http)
open
http://104.21.58.16:2082/
Http-Status: 403
Forbidden

104.21.58.16
2083
cPanel (https)
open
https://104.21.58.16:2083/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

104.21.58.16
2083
cPanel (https)
open
https://104.21.58.16:2083/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

104.21.58.16
2086
WHM (http)
open
http://104.21.58.16:2086/
Http-Status: 403
Forbidden

104.21.58.16
2086
WHM (http)
open
http://104.21.58.16:2086/
Http-Status: 403
Forbidden

104.21.58.16
2087
WHM (https)
open
https://104.21.58.16:2087/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

104.21.58.16
2087
WHM (https)
open
https://104.21.58.16:2087/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

104.21.58.16
2089
cPanel Licensing



104.21.58.16
2089
cPanel Licensing



104.21.58.16
2095
cPanel Webmail (http)
open
http://104.21.58.16:2095/
Http-Status: 403
Forbidden

104.21.58.16
2095
cPanel Webmail (http)
open
http://104.21.58.16:2095/
Http-Status: 403
Forbidden

104.21.58.16
2096
cPanel Webmail (https)
open
https://104.21.58.16:2096/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

104.21.58.16
2096
cPanel Webmail (https)
open
https://104.21.58.16:2096/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

104.21.58.16
2222
DirectAdmin (http)



104.21.58.16
2222
DirectAdmin (http)



104.21.58.16
2222
DirectAdmin (https)



104.21.58.16
2222
DirectAdmin (https)



104.21.58.16
3306
mySql



104.21.58.16
3306
mySql



104.21.58.16
5224
Plesk Licensing



104.21.58.16
5224
Plesk Licensing



104.21.58.16
5432
PostgreSQL



104.21.58.16
5432
PostgreSQL



104.21.58.16
8080
Ookla Speedtest (http)
open
http://104.21.58.16:8080/
Http-Status: 403
Forbidden

104.21.58.16
8080
Ookla Speedtest (http)
open
http://104.21.58.16:8080/
Http-Status: 403
Forbidden

104.21.58.16
8080
Ookla Speedtest (https)
open
https://104.21.58.16:8080/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

104.21.58.16
8080
Ookla Speedtest (https)
open
https://104.21.58.16:8080/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

104.21.58.16
8083
VestaCP http



104.21.58.16
8083
VestaCP http



104.21.58.16
8083
VestaCP https



104.21.58.16
8083
VestaCP https



104.21.58.16
8443
Plesk Administration (https)
open
https://104.21.58.16:8443/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

104.21.58.16
8443
Plesk Administration (https)
open
https://104.21.58.16:8443/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

104.21.58.16
8447
Plesk Installer + Updates



104.21.58.16
8447
Plesk Installer + Updates



104.21.58.16
8880
Plesk Administration (http)
open
http://104.21.58.16:8880/
Http-Status: 403
Forbidden

104.21.58.16
8880
Plesk Administration (http)
open
http://104.21.58.16:8880/
Http-Status: 403
Forbidden

104.21.58.16
10000
Webmin (http)



104.21.58.16
10000
Webmin (http)



104.21.58.16
10000
Webmin (https)



104.21.58.16
10000
Webmin (https)



172.67.197.52
21
FTP



172.67.197.52
21
FTP



172.67.197.52
22
SSH



172.67.197.52
22
SSH



172.67.197.52
25
SMTP



172.67.197.52
25
SMTP



172.67.197.52
53
DNS



172.67.197.52
53
DNS



172.67.197.52
110
POP3



172.67.197.52
110
POP3



172.67.197.52
143
IMAP



172.67.197.52
143
IMAP



172.67.197.52
465
SMTP (encrypted)



172.67.197.52
465
SMTP (encrypted)



172.67.197.52
587
SMTP (encrypted, submission)



172.67.197.52
587
SMTP (encrypted, submission)



172.67.197.52
993
IMAP (encrypted)



172.67.197.52
993
IMAP (encrypted)



172.67.197.52
995
POP3 (encrypted)



172.67.197.52
995
POP3 (encrypted)



172.67.197.52
1433
MS SQL



172.67.197.52
1433
MS SQL



172.67.197.52
2082
cPanel (http)
open
http://172.67.197.52:2082/
Http-Status: 403
Forbidden

172.67.197.52
2082
cPanel (http)
open
http://172.67.197.52:2082/
Http-Status: 403
Forbidden

172.67.197.52
2083
cPanel (https)
open
https://172.67.197.52:2083/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

172.67.197.52
2083
cPanel (https)
open
https://172.67.197.52:2083/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

172.67.197.52
2086
WHM (http)
open
http://172.67.197.52:2086/
Http-Status: 403
Forbidden

172.67.197.52
2086
WHM (http)
open
http://172.67.197.52:2086/
Http-Status: 403
Forbidden

172.67.197.52
2087
WHM (https)
open
https://172.67.197.52:2087/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

172.67.197.52
2087
WHM (https)
open
https://172.67.197.52:2087/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

172.67.197.52
2089
cPanel Licensing



172.67.197.52
2089
cPanel Licensing



172.67.197.52
2095
cPanel Webmail (http)
open
http://172.67.197.52:2095/
Http-Status: 403
Forbidden

172.67.197.52
2095
cPanel Webmail (http)
open
http://172.67.197.52:2095/
Http-Status: 403
Forbidden

172.67.197.52
2096
cPanel Webmail (https)
open
https://172.67.197.52:2096/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

172.67.197.52
2096
cPanel Webmail (https)
open
https://172.67.197.52:2096/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

172.67.197.52
2222
DirectAdmin (http)



172.67.197.52
2222
DirectAdmin (http)



172.67.197.52
2222
DirectAdmin (https)



172.67.197.52
2222
DirectAdmin (https)



172.67.197.52
3306
mySql



172.67.197.52
3306
mySql



172.67.197.52
5224
Plesk Licensing



172.67.197.52
5224
Plesk Licensing



172.67.197.52
5432
PostgreSQL



172.67.197.52
5432
PostgreSQL



172.67.197.52
8080
Ookla Speedtest (http)
open
http://172.67.197.52:8080/
Http-Status: 403
Forbidden

172.67.197.52
8080
Ookla Speedtest (http)
open
http://172.67.197.52:8080/
Http-Status: 403
Forbidden

172.67.197.52
8080
Ookla Speedtest (https)
open
https://172.67.197.52:8080/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

172.67.197.52
8080
Ookla Speedtest (https)
open
https://172.67.197.52:8080/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

172.67.197.52
8083
VestaCP http



172.67.197.52
8083
VestaCP http



172.67.197.52
8083
VestaCP https



172.67.197.52
8083
VestaCP https



172.67.197.52
8443
Plesk Administration (https)
open
https://172.67.197.52:8443/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

172.67.197.52
8443
Plesk Administration (https)
open
https://172.67.197.52:8443/
Http-Status: -10
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

172.67.197.52
8447
Plesk Installer + Updates



172.67.197.52
8447
Plesk Installer + Updates



172.67.197.52
8880
Plesk Administration (http)
open
http://172.67.197.52:8880/
Http-Status: 403
Forbidden

172.67.197.52
8880
Plesk Administration (http)
open
http://172.67.197.52:8880/
Http-Status: 403
Forbidden

172.67.197.52
10000
Webmin (http)



172.67.197.52
10000
Webmin (http)



172.67.197.52
10000
Webmin (https)



172.67.197.52
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=bc5bbec9-1f08-4a05-b658-bb1260df13d2


Last Result: https://check-your-website.server-daten.de/?q=bitwarden.samsepi0l.ovh - 2022-01-14 20:09: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=bitwarden.samsepi0l.ovh" target="_blank">Check this Site: bitwarden.samsepi0l.ovh</a>