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




V

Connect failure - perhaps firewall

Checked:
18.03.2023 15:31:06


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
binance.nemomen.fr
A
139.99.101.236
Singapore/Central Singapore/Singapore (SG) - OVH Hosting
Hostname: vps-af6378b3.vps.ovh.ca
yes
1
0

AAAA
2402:1f00:8000:800::94c
Singapore/North West/Singapore (SG) - OVH SAS

yes


www.binance.nemomen.fr

Name Error
yes
1
0
*.nemomen.fr
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.binance.nemomen.fr
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 951, 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: 02.04.2023, 00:00:00 +, Signature-Inception: 12.03.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: fr
fr
1 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 51508, DigestType 2 and Digest GzOGhk0wzMj0VBuYW/LKMg5PUsV8UzU/bSnJrVilZx8=



1 RRSIG RR to validate DS RR found



RRSIG-Owner fr., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 31.03.2023, 05:00:00 +, Signature-Inception: 18.03.2023, 04:00:00 +, KeyTag 951, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 13, KeyTag 62771, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner fr., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 06.04.2023, 01:13:13 +, Signature-Inception: 13.03.2023, 13:58:46 +, KeyTag 51508, Signer-Name: fr



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



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

Zone: nemomen.fr
nemomen.fr
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 "kudd65koedoaeei97l6bn6u12a9dcilf" between the hashed NSEC3-owner "kud8jet1t5cbo6p5h2ngjo92o4k88ggl" and the hashed NextOwner "kuddr8cr91jek1n57d4rjilsee3gfodu". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner kud8jet1t5cbo6p5h2ngjo92o4k88ggl.fr., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 12.05.2023, 20:06:55 +, Signature-Inception: 09.03.2023, 07:55:30 +, KeyTag 62771, Signer-Name: fr



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "sfblg7nfatq81cqjgt5q91bqs3h9v6nd" as Owner. That's the Hash of "fr" with the NextHashedOwnerName "sfbn9rjnnuevsb0gner878n1gn41d23i". So that domain name is the Closest Encloser of "nemomen.fr". Opt-Out: True.
Bitmap: NS, SOA, TXT, NAPTR, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner sfblg7nfatq81cqjgt5q91bqs3h9v6nd.fr., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 28.04.2023, 17:09:02 +, Signature-Inception: 09.03.2023, 07:55:30 +, KeyTag 62771, Signer-Name: fr



0 DNSKEY RR found




Zone: binance.nemomen.fr
binance.nemomen.fr
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.binance.nemomen.fr
www.binance.nemomen.fr
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.binance.nemomen.fr
  ns1.gandi.net

binance.nemomen.fr
  ns1.gandi.net / node-amsterdam1
173.246.100.2
Paris/Île-de-France/France (FR) - Gandi US Inc


 
2001:4b98:aaaa::2
Paris/Île-de-France/France (FR) - GANDI is an ICANN accredited registrar

nemomen.fr
  ns1.gandi.net


  ns-121-c.gandi.net / node-amsterdam1
217.70.187.122
Paris/Île-de-France/France (FR) - Gandi SAS


 
2604:3400:aaac::7a
Paris/Île-de-France/France (FR) - Gandi US Inc


  ns-135-a.gandi.net / node-amsterdam1
173.246.100.136
Paris/Île-de-France/France (FR) - Gandi US Inc


 
2001:4b98:aaaa::88
Paris/Île-de-France/France (FR) - GANDI is an ICANN accredited registrar


  ns-173-b.gandi.net / node-amsterdam1
213.167.230.174
Paris/Île-de-France/France (FR) - Gandi SAS


 
2001:4b98:aaab::ae
Paris/Île-de-France/France (FR) - GANDI is an ICANN accredited registrar

fr
  a.nic.fr


  d.nic.fr / dns.ams.nic.fr


  e.ext.nic.fr / ops-nsext01-p.sidn.nl


  f.ext.nic.fr / s2.wie


  g.ext.nic.fr / 1.ber.pch


4. SOA-Entries


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


Domain:fr
Zone-Name:fr
Primary:a.nic.fr
Mail:dnsmaster.afnic.fr
Serial:2235126187
Refresh:3600
Retry:1800
Expire:3600000
TTL:600
num Entries:1


Domain:fr
Zone-Name:fr
Primary:a.nic.fr
Mail:dnsmaster.afnic.fr
Serial:2235126195
Refresh:3600
Retry:1800
Expire:3600000
TTL:600
num Entries:3


Domain:nemomen.fr
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:nemomen.fr
Zone-Name:nemomen.fr
Primary:ns1.gandi.net
Mail:hostmaster.gandi.net
Serial:1678924800
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:6


Domain:binance.nemomen.fr
Zone-Name:nemomen.fr
Primary:ns1.gandi.net
Mail:hostmaster.gandi.net
Serial:1664307861
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:2


Domain:www.binance.nemomen.fr
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because Chrome (used to create the Screenshot) could not load the url. Instead, there was a redirect to "chrome-error://chromewebdata/", so the content of your website isn't visible.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://binance.nemomen.fr/
139.99.101.236
-2

1.523
V
ConnectFailure - Unable to connect to the remote server

• http://binance.nemomen.fr/
2402:1f00:8000:800::94c
-14

10.040
T
Timeout - The operation has timed out

• https://binance.nemomen.fr/
139.99.101.236 No GZip used - 531 / 654 - 81.19 % possible
Inline-JavaScript (∑/total): 1/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 112.95 %
5.824
N
Certificate error: RemoteCertificateChainErrors
small visible content (num chars: 102)
We're sorry but FreqUI doesn't work properly without JavaScript enabled. Please enable it to continue.
Server: nginx/1.23.3
Date: Sat, 18 Mar 2023 14:31:56 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 654
Connection: close
last-modified: Fri, 17 Mar 2023 06:31:26 GMT
etag: 7318d6d53b1c464d27cfc1a8505208e3
Strict-Transport-Security: max-age=31536000

• https://binance.nemomen.fr/
2402:1f00:8000:800::94c
-14

10.033
T
Timeout - The operation has timed out

• http://binance.nemomen.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
139.99.101.236
-2

1.780
V
ConnectFailure - Unable to connect to the remote server
Visible Content:

• http://binance.nemomen.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2402:1f00:8000:800::94c
-14

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

• https://139.99.101.236/
139.99.101.236
503

Html is minified: 107.65 %
5.957
N
Service Temporarily Unavailable
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Server: nginx/1.23.3
Date: Sat, 18 Mar 2023 14:32:26 GMT
Content-Type: text/html
Content-Length: 197
Connection: close

• https://[2402:1f00:8000:0800:0000:0000:0000:094c]/
2402:1f00:8000:800::94c
-14

10.033
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "binance.nemomen.fr" is subdomain, public suffix is ".fr", top-level-domain is ".fr", top-level-domain-type is "country-code", Country is France, tld-manager is "Association Française pour le Nommage Internet en Coopération (A.F.N.I.C.)", num .fr-domains preloaded: 2986 (complete: 220007)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: binance.nemomen.fr has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: binance.nemomen.fr has 1 ipv4, 1 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
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ihttps://binance.nemomen.fr/ 139.99.101.236
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
Khttp://binance.nemomen.fr/ 139.99.101.236, Status -2

http://binance.nemomen.fr/ 2402:1f00:8000:800::94c, Status -14
Configuration problem - different ip addresses with different status
Khttps://binance.nemomen.fr/ 139.99.101.236, Status 200

https://binance.nemomen.fr/ 2402:1f00:8000:800::94c, Status -14
Configuration problem - different ip addresses with different status
Khttp://binance.nemomen.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 139.99.101.236, Status -2

http://binance.nemomen.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2402:1f00:8000:800::94c, Status -14
Configuration problem - different ip addresses with different status
Nhttps://binance.nemomen.fr/ 139.99.101.236
200

Error - Certificate isn't trusted, RemoteCertificateChainErrors
Nhttps://139.99.101.236/ 139.99.101.236
503

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Vhttp://binance.nemomen.fr/ 139.99.101.236
-2

Connect failure - perhaps firewall
Vhttp://binance.nemomen.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 139.99.101.236
-2

Connect failure - perhaps firewall
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain binance.nemomen.fr, 2 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.binance.nemomen.fr

2. Header-Checks

Fbinance.nemomen.fr 139.99.101.236
Content-Security-Policy
Critical: Missing Header:
Fbinance.nemomen.fr 139.99.101.236
X-Content-Type-Options
Critical: Missing Header:
Fbinance.nemomen.fr 139.99.101.236
Referrer-Policy
Critical: Missing Header:
Fbinance.nemomen.fr 139.99.101.236
Permissions-Policy
Critical: Missing Header:

3. DNS- and NameServer - Checks

AInfo:: 10 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 10 Queries complete, 10 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns1.gandi.net, ns-121-c.gandi.net, ns-135-a.gandi.net, ns-173-b.gandi.net, 3 Name Servers included in Delegation: ns-121-c.gandi.net, ns-135-a.gandi.net, ns-173-b.gandi.net, 3 Name Servers included in 2 Zone definitions: ns-121-c.gandi.net, ns-135-a.gandi.net, ns-173-b.gandi.net, 1 Name Servers listed in SOA.Primary: ns1.gandi.net.
AGood: Only one SOA.Primary Name Server found.: ns1.gandi.net.
Error: SOA.Primary Name Server not included in the delegation set.: ns1.gandi.net.
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: ns-121-c.gandi.net, ns-135-a.gandi.net, ns-173-b.gandi.net
AGood: All Name Server Domain Names have a Public Suffix.
Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1

AGood: Minimal 2 different name servers (public suffix and public ip address) found: 3 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 3 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.: 3 Name Servers, 1 Top Level Domain: net
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: gandi.net
Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: FR
AInfo: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 173., 213., 217., 3 different subnets (first two Bytes): 173.246., 213.167., 217.70., 3 different subnets (first three Bytes): 173.246.100., 213.167.230., 217.70.187.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2604:, 2 different subnets (first two blocks): 2001:4b98:, 2604:3400:, 3 different subnets (first three blocks): 2001:4b98:aaaa:, 2001:4b98:aaab:, 2604:3400:aaac:, 3 different subnets (first four blocks): 2001:4b98:aaaa:0000:, 2001:4b98:aaab:0000:, 2604:3400:aaac:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: a.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: d.nic.fr: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns.ams.nic.fr). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.gandi.net: 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: ns1.gandi.net: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

http://binance.nemomen.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2402:1f00:8000:800::94c
-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://binance.nemomen.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 139.99.101.236
-2

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://binance.nemomen.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2402:1f00:8000:800::94c, Status -14

http://binance.nemomen.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 139.99.101.236, Status -2
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
https://binance.nemomen.fr/ 139.99.101.236
200

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

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
https://binance.nemomen.fr/ 139.99.101.236
200

Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 1 script elements without defer/async.
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 2 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 2 complete.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
AInfo: No img element found, no alt attribute checked
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 580050 milliseconds, 580.050 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
binance.nemomen.fr
139.99.101.236
443
Certificate/chain invalid
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
binance.nemomen.fr
139.99.101.236
443
Certificate/chain invalid
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
Chain - too much certificates, don't send root certificates
1CN=binance.nemomen.fr

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

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


139.99.101.236
139.99.101.236
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

139.99.101.236
139.99.101.236
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
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=letsencrypt-nginx-proxy-companion


9. Certificates

1.
1.
CN=binance.nemomen.fr
27.09.2022
26.12.2022
517 days expired
binance.nemomen.fr - 1 entry
1.
1.
CN=binance.nemomen.fr
27.09.2022

26.12.2022
517 days expired
binance.nemomen.fr - 1 entry

KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0397AAFBBEF985A0D57A8BC649DD87D56B97
Thumbprint:ADC067508193F6248FC017FD5AC20582E7210008
SHA256 / Certificate:fzcCWrcPL8mY/R+VyYRZDzjgCHfugY9aOJnUzS0mzT0=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):7a94baa9726e4e76e4e5f9943b77ab3ddfa99fcde829d237f0161519b36d26c4
SHA256 hex / Subject Public Key Information (SPKI):7a94baa9726e4e76e4e5f9943b77ab3ddfa99fcde829d237f0161519b36d26c4 (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)

NotTimeValid: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
RevocationStatusUnknown: The revocation function was unable to check revocation for the certificate.
OfflineRevocation: The revocation function was unable to check revocation because the revocation server was offline.

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


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

15.09.2025
expires in 477 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 4026 days


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

04.06.2035
expires in 4026 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=letsencrypt-nginx-proxy-companion
27.09.2022
27.09.2023
242 days expired

2.
1.
CN=letsencrypt-nginx-proxy-companion
27.09.2022

27.09.2023
242 days expired


KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:2C5EB1C47D50D484443A48916312C82BC7F4C3CC
Thumbprint:638229E7B7359A67B19C1586EFA7644337A55EA3
SHA256 / Certificate:2LknHqEo+YrIAP/k56g4ISZZBm9l5LBHLwgJPODSvlw=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):e3281f79d0079e0d2e3236d5774faa874a008dc1c70757e5cbb8578d88500cbe
SHA256 hex / Subject Public Key Information (SPKI):e3281f79d0079e0d2e3236d5774faa874a008dc1c70757e5cbb8578d88500cbe (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:

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

Small Code Update - wait one minute


11. Html-Content - Entries

Summary

Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://binance.nemomen.fr/
139.99.101.236
link
stylesheet
1

1
1
0
0
0
0


link
other
1

1
1
0
0
0
0


meta
other
3

0


0
0
0


script

1

1
1
0
0
0
0

Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
https://binance.nemomen.fr/
139.99.101.236
link
icon
/favicon.ico
-2
ConnectFailure - Unable to connect to the remote server
1
ConnectFailure - Unable to connect to the remote server








link
stylesheet
/assets/index.10d8c430.css
-2
ConnectFailure - Unable to connect to the remote server
1
ConnectFailure - Unable to connect to the remote server








meta

utf-8


1
ok








meta
X-UA-Compatible
IE=edge


1
ok








meta
viewport
width=device-width,initial-scale=1.0


1
ok








script
src
/assets/index.1d9ad345.js
-2
ConnectFailure - Unable to connect to the remote server
1
ConnectFailure - Unable to connect to the remote server
Missing defer / async attribute.








12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns-121-c.gandi.net, ns-135-a.gandi.net, ns-173-b.gandi.net

QNr.DomainTypeNS used
1
net
NS
h.root-servers.net (2001:500:1::53)

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

Answer: dns0.gandi.net, dns1.gandi.net, dns2.gandi.net, dns3.gandi.net, dns4.gandi.net, dns6.gandi.net

Answer: dns6.gandi.net
162.159.24.111, 162.159.25.213, 2400:cb00:2049:1::a29f:186f, 2400:cb00:2049:1::a29f:19d5

Answer: dns4.gandi.net
2001:4b98:dc2:90:217:70:186:184, 217.70.186.184

Answer: dns3.gandi.net
2001:4b98:c:13::14, 217.70.184.14

Answer: dns2.gandi.net
2001:4b98:d:589::211, 217.70.183.211

Answer: dns1.gandi.net
2001:4b98:d:1::45, 217.70.177.45

Answer: dns0.gandi.net
2001:4b98:d:1::39, 217.70.177.39
3
ns-135-a.gandi.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns0.gandi.net, dns1.gandi.net, dns2.gandi.net, dns3.gandi.net, dns4.gandi.net, dns6.gandi.net

Answer: dns6.gandi.net
162.159.24.111, 162.159.25.213, 2400:cb00:2049:1::a29f:186f, 2400:cb00:2049:1::a29f:19d5

Answer: dns4.gandi.net
2001:4b98:dc2:90:217:70:186:184, 217.70.186.184

Answer: dns3.gandi.net
2001:4b98:c:13::14, 217.70.184.14

Answer: dns2.gandi.net
2001:4b98:d:589::211, 217.70.183.211

Answer: dns1.gandi.net
2001:4b98:d:1::45, 217.70.177.45

Answer: dns0.gandi.net
2001:4b98:d:1::39, 217.70.177.39
4
ns-173-b.gandi.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns0.gandi.net, dns1.gandi.net, dns2.gandi.net, dns3.gandi.net, dns4.gandi.net, dns6.gandi.net

Answer: dns6.gandi.net
162.159.24.111, 162.159.25.213, 2400:cb00:2049:1::a29f:186f, 2400:cb00:2049:1::a29f:19d5

Answer: dns4.gandi.net
2001:4b98:dc2:90:217:70:186:184, 217.70.186.184

Answer: dns3.gandi.net
2001:4b98:c:13::14, 217.70.184.14

Answer: dns2.gandi.net
2001:4b98:d:589::211, 217.70.183.211

Answer: dns1.gandi.net
2001:4b98:d:1::45, 217.70.177.45

Answer: dns0.gandi.net
2001:4b98:d:1::39, 217.70.177.39
5
ns-121-c.gandi.net: 217.70.187.122
A
dns0.gandi.net (2001:4b98:d:1::39)
6
ns-121-c.gandi.net: 2604:3400:aaac::7a
AAAA
dns0.gandi.net (2001:4b98:d:1::39)
7
ns-135-a.gandi.net: 173.246.100.136
A
dns0.gandi.net (2001:4b98:d:1::39)
8
ns-135-a.gandi.net: 2001:4b98:aaaa::88
AAAA
dns0.gandi.net (2001:4b98:d:1::39)
9
ns-173-b.gandi.net: 213.167.230.174
A
dns0.gandi.net (2001:4b98:d:1::39)
10
ns-173-b.gandi.net: 2001:4b98:aaab::ae
AAAA
dns0.gandi.net (2001:4b98:d:1::39)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
binance.nemomen.fr
0

no CAA entry found
1
0
nemomen.fr
0

no CAA entry found
1
0
fr
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
nemomen.fr
v=spf1 include:_mailcust.gandi.net ?all
ok
1
0
binance.nemomen.fr

ok
1
0
_acme-challenge.binance.nemomen.fr

Name Error - The domain name does not exist
1
0
_acme-challenge.binance.nemomen.fr.nemomen.fr

Name Error - The domain name does not exist
1
0
_acme-challenge.binance.nemomen.fr.binance.nemomen.fr

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites

DomainIPPortCipher (OpenSsl / IANA)
binance.nemomen.fr
139.99.101.236
443
234 Cipher Suites checked, no connection possible.
0 Ciphers, 354.11 sec





17. Portchecks

DomainIPPortDescriptionResultAnswer
binance.nemomen.fr
139.99.101.236
21
FTP



binance.nemomen.fr
139.99.101.236
21
FTP



binance.nemomen.fr
139.99.101.236
22
SSH
open
SSH-2.0-OpenSSH_8.4p1 Ubuntu-6ubuntu2

binance.nemomen.fr
139.99.101.236
22
SSH
open
SSH-2.0-OpenSSH_8.4p1 Ubuntu-6ubuntu2
Bad: SSH without DNS SSHFP Record found
Possible DNS SSHFP Entries:
binance.nemomen.fr IN SSHFP 1 2 9abac74bef84aa3d8c779be0d6b17938a5c458ca7b8a4318d724e5a483d4c054
binance.nemomen.fr IN SSHFP 3 2 b92410be9edfc143eb06a64362943552db455ce44b0994a06356565a8c661b38
binance.nemomen.fr IN SSHFP 4 2 5c2dc75e5d79bc9e71d4f9e5ae9ae09d506b5525def0137237e800b35c9ae39e
binance.nemomen.fr
139.99.101.236
25
SMTP



binance.nemomen.fr
139.99.101.236
25
SMTP



binance.nemomen.fr
139.99.101.236
53
DNS



binance.nemomen.fr
139.99.101.236
53
DNS



binance.nemomen.fr
139.99.101.236
110
POP3



binance.nemomen.fr
139.99.101.236
110
POP3



binance.nemomen.fr
139.99.101.236
143
IMAP



binance.nemomen.fr
139.99.101.236
143
IMAP



binance.nemomen.fr
139.99.101.236
465
SMTP (encrypted)



binance.nemomen.fr
139.99.101.236
465
SMTP (encrypted)



binance.nemomen.fr
139.99.101.236
587
SMTP (encrypted, submission)



binance.nemomen.fr
139.99.101.236
587
SMTP (encrypted, submission)



binance.nemomen.fr
139.99.101.236
993
IMAP (encrypted)



binance.nemomen.fr
139.99.101.236
993
IMAP (encrypted)



binance.nemomen.fr
139.99.101.236
995
POP3 (encrypted)



binance.nemomen.fr
139.99.101.236
995
POP3 (encrypted)



binance.nemomen.fr
139.99.101.236
1433
MS SQL



binance.nemomen.fr
139.99.101.236
1433
MS SQL



binance.nemomen.fr
139.99.101.236
2082
cPanel (http)



binance.nemomen.fr
139.99.101.236
2082
cPanel (http)



binance.nemomen.fr
139.99.101.236
2083
cPanel (https)



binance.nemomen.fr
139.99.101.236
2083
cPanel (https)



binance.nemomen.fr
139.99.101.236
2086
WHM (http)



binance.nemomen.fr
139.99.101.236
2086
WHM (http)



binance.nemomen.fr
139.99.101.236
2087
WHM (https)



binance.nemomen.fr
139.99.101.236
2087
WHM (https)



binance.nemomen.fr
139.99.101.236
2089
cPanel Licensing



binance.nemomen.fr
139.99.101.236
2089
cPanel Licensing



binance.nemomen.fr
139.99.101.236
2095
cPanel Webmail (http)



binance.nemomen.fr
139.99.101.236
2095
cPanel Webmail (http)



binance.nemomen.fr
139.99.101.236
2096
cPanel Webmail (https)



binance.nemomen.fr
139.99.101.236
2096
cPanel Webmail (https)



binance.nemomen.fr
139.99.101.236
2222
DirectAdmin (http)



binance.nemomen.fr
139.99.101.236
2222
DirectAdmin (http)



binance.nemomen.fr
139.99.101.236
2222
DirectAdmin (https)



binance.nemomen.fr
139.99.101.236
2222
DirectAdmin (https)



binance.nemomen.fr
139.99.101.236
3306
mySql



binance.nemomen.fr
139.99.101.236
3306
mySql



binance.nemomen.fr
139.99.101.236
5224
Plesk Licensing



binance.nemomen.fr
139.99.101.236
5224
Plesk Licensing



binance.nemomen.fr
139.99.101.236
5432
PostgreSQL



binance.nemomen.fr
139.99.101.236
5432
PostgreSQL



binance.nemomen.fr
139.99.101.236
8080
Ookla Speedtest (http)



binance.nemomen.fr
139.99.101.236
8080
Ookla Speedtest (http)



binance.nemomen.fr
139.99.101.236
8080
Ookla Speedtest (https)



binance.nemomen.fr
139.99.101.236
8080
Ookla Speedtest (https)



binance.nemomen.fr
139.99.101.236
8083
VestaCP http



binance.nemomen.fr
139.99.101.236
8083
VestaCP http



binance.nemomen.fr
139.99.101.236
8083
VestaCP https



binance.nemomen.fr
139.99.101.236
8083
VestaCP https



binance.nemomen.fr
139.99.101.236
8443
Plesk Administration (https)



binance.nemomen.fr
139.99.101.236
8443
Plesk Administration (https)



binance.nemomen.fr
139.99.101.236
8447
Plesk Installer + Updates



binance.nemomen.fr
139.99.101.236
8447
Plesk Installer + Updates



binance.nemomen.fr
139.99.101.236
8880
Plesk Administration (http)



binance.nemomen.fr
139.99.101.236
8880
Plesk Administration (http)



binance.nemomen.fr
139.99.101.236
10000
Webmin (http)



binance.nemomen.fr
139.99.101.236
10000
Webmin (http)



binance.nemomen.fr
139.99.101.236
10000
Webmin (https)



binance.nemomen.fr
139.99.101.236
10000
Webmin (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
21
FTP



binance.nemomen.fr
2402:1f00:8000:800::94c
21
FTP



binance.nemomen.fr
2402:1f00:8000:800::94c
22
SSH



binance.nemomen.fr
2402:1f00:8000:800::94c
22
SSH



binance.nemomen.fr
2402:1f00:8000:800::94c
25
SMTP



binance.nemomen.fr
2402:1f00:8000:800::94c
25
SMTP



binance.nemomen.fr
2402:1f00:8000:800::94c
53
DNS



binance.nemomen.fr
2402:1f00:8000:800::94c
53
DNS



binance.nemomen.fr
2402:1f00:8000:800::94c
110
POP3



binance.nemomen.fr
2402:1f00:8000:800::94c
110
POP3



binance.nemomen.fr
2402:1f00:8000:800::94c
143
IMAP



binance.nemomen.fr
2402:1f00:8000:800::94c
143
IMAP



binance.nemomen.fr
2402:1f00:8000:800::94c
465
SMTP (encrypted)



binance.nemomen.fr
2402:1f00:8000:800::94c
465
SMTP (encrypted)



binance.nemomen.fr
2402:1f00:8000:800::94c
587
SMTP (encrypted, submission)



binance.nemomen.fr
2402:1f00:8000:800::94c
587
SMTP (encrypted, submission)



binance.nemomen.fr
2402:1f00:8000:800::94c
993
IMAP (encrypted)



binance.nemomen.fr
2402:1f00:8000:800::94c
993
IMAP (encrypted)



binance.nemomen.fr
2402:1f00:8000:800::94c
995
POP3 (encrypted)



binance.nemomen.fr
2402:1f00:8000:800::94c
995
POP3 (encrypted)



binance.nemomen.fr
2402:1f00:8000:800::94c
1433
MS SQL



binance.nemomen.fr
2402:1f00:8000:800::94c
1433
MS SQL



binance.nemomen.fr
2402:1f00:8000:800::94c
2082
cPanel (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
2082
cPanel (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
2083
cPanel (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
2083
cPanel (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
2086
WHM (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
2086
WHM (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
2087
WHM (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
2087
WHM (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
2089
cPanel Licensing



binance.nemomen.fr
2402:1f00:8000:800::94c
2089
cPanel Licensing



binance.nemomen.fr
2402:1f00:8000:800::94c
2095
cPanel Webmail (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
2095
cPanel Webmail (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
2096
cPanel Webmail (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
2096
cPanel Webmail (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
2222
DirectAdmin (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
2222
DirectAdmin (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
2222
DirectAdmin (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
2222
DirectAdmin (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
3306
mySql



binance.nemomen.fr
2402:1f00:8000:800::94c
3306
mySql



binance.nemomen.fr
2402:1f00:8000:800::94c
5224
Plesk Licensing



binance.nemomen.fr
2402:1f00:8000:800::94c
5224
Plesk Licensing



binance.nemomen.fr
2402:1f00:8000:800::94c
5432
PostgreSQL



binance.nemomen.fr
2402:1f00:8000:800::94c
5432
PostgreSQL



binance.nemomen.fr
2402:1f00:8000:800::94c
8080
Ookla Speedtest (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
8080
Ookla Speedtest (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
8080
Ookla Speedtest (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
8080
Ookla Speedtest (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
8083
VestaCP http



binance.nemomen.fr
2402:1f00:8000:800::94c
8083
VestaCP http



binance.nemomen.fr
2402:1f00:8000:800::94c
8083
VestaCP https



binance.nemomen.fr
2402:1f00:8000:800::94c
8083
VestaCP https



binance.nemomen.fr
2402:1f00:8000:800::94c
8443
Plesk Administration (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
8443
Plesk Administration (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
8447
Plesk Installer + Updates



binance.nemomen.fr
2402:1f00:8000:800::94c
8447
Plesk Installer + Updates



binance.nemomen.fr
2402:1f00:8000:800::94c
8880
Plesk Administration (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
8880
Plesk Administration (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
10000
Webmin (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
10000
Webmin (http)



binance.nemomen.fr
2402:1f00:8000:800::94c
10000
Webmin (https)



binance.nemomen.fr
2402:1f00:8000:800::94c
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=db54ab16-2e8d-4e6c-bf2e-60dd43a04749


Last Result: https://check-your-website.server-daten.de/?q=binance.nemomen.fr - 2023-03-18 15:31:06


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

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

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