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

0 in Queue, 0 of max. 4 Checks (23:11:34)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A


Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. NameServer-IPAddresses | 13. CAA | 14. TXT | 15. DomainServiceEntries | 16. Cipher Suites | 17. Portchecks |


V

Connect failure - perhaps firewall

Checked:
19.06.2022 13:27:27


Older results

N - 15.02.2021 20:07:24

H - 15.02.2021 16:18:30

H - 15.02.2021 16:06:11

H - 10.02.2021 11:23:22

N - 09.02.2021 17:00:13

T - 30.11.2020 16:16:32

T - 07.04.2020 16:08:47

T - 07.04.2020 16:01:08

T - 24.03.2020 11:30:25

H - 22.03.2020 01:03:51


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
mydomoticz.ovh
A
213.186.33.5
Roubaix/Hauts-de-France/France (FR) - OVH SAS
Hostname: redirect.ovh.net
yes
1
0

AAAA

yes


www.mydomoticz.ovh
A
213.186.33.5
Roubaix/Hauts-de-France/France (FR) - OVH SAS
Hostname: redirect.ovh.net
yes
1
0

AAAA

yes


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



Public Key with Algorithm 8, KeyTag 47671, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.07.2022, 00:00:00 +, Signature-Inception: 10.06.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: 02.07.2022, 05:00:00 +, Signature-Inception: 19.06.2022, 04:00:00 +, KeyTag 47671, Signer-Name: (root)



• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 47671 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 10246, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ovh., Algorithm: 13, 1 Labels, original TTL: 172800 sec, Signature-expiration: 23.07.2022, 14:07:15 +, Signature-Inception: 19.06.2022, 10:20: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: mydomoticz.ovh
mydomoticz.ovh
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 7939, DigestType 2 and Digest dmRuK+qJm6as3qrzFzuuVNN8iHzl57xvig3Eucr18NA=



1 RRSIG RR to validate DS RR found



RRSIG-Owner mydomoticz.ovh., Algorithm: 13, 2 Labels, original TTL: 172800 sec, Signature-expiration: 11.07.2022, 22:41:21 +, Signature-Inception: 29.05.2022, 10:20:11 +, KeyTag 10246, Signer-Name: ovh



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 4413, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner mydomoticz.ovh., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



RRSIG-Owner mydomoticz.ovh., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 7939, Signer-Name: mydomoticz.ovh



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



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



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



RRSIG Type 1 validates the A - Result: 213.186.33.5
Validated: RRSIG-Owner mydomoticz.ovh., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



RRSIG Type 16 validates the TXT - Result: 1|www.mydomoticz.ovh
Validated: RRSIG-Owner mydomoticz.ovh., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "cefcsqilefcimiaabd0dn0644hnvdta3" equal the hashed NSEC3-owner "cefcsqilefcimiaabd0dn0644hnvdta3" and the hashed NextOwner "fnfabkf6gr4lbq8rm6ndmcncgitcl07l". 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, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner cefcsqilefcimiaabd0dn0644hnvdta3.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "cefcsqilefcimiaabd0dn0644hnvdta3" equal the hashed NSEC3-owner "cefcsqilefcimiaabd0dn0644hnvdta3" and the hashed NextOwner "fnfabkf6gr4lbq8rm6ndmcncgitcl07l". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner cefcsqilefcimiaabd0dn0644hnvdta3.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.mydomoticz.ovh) sends a valid NSEC3 RR as result with the hashed owner name "brfqu765ebpllugefjose0evklukegpl" (unhashed: _tcp.mydomoticz.ovh). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner brfqu765ebpllugefjose0evklukegpl.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



Status: Good. NXDomain-Proof required and found.



TLSA-Query (_443._tcp.mydomoticz.ovh) sends a valid NSEC3 RR as result with the hashed query name "d51poconhp8bjkuqhqltl5ka1ecef5l8" between the hashed NSEC3-owner "cefcsqilefcimiaabd0dn0644hnvdta3" and the hashed NextOwner "fnfabkf6gr4lbq8rm6ndmcncgitcl07l". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner cefcsqilefcimiaabd0dn0644hnvdta3.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "84k0m8ro1kq28a61t2bl7s299khurgdt" (unhashed: *._tcp.mydomoticz.ovh) with the owner "7jk0tlj8meh2bqk0vc3am4uptc6oblqj" and the NextOwner "8rt9mfgj6r3a05kmui36352oa9c4h508". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: SRV, RRSIG Validated: RRSIG-Owner 7jk0tlj8meh2bqk0vc3am4uptc6oblqj.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "cefcsqilefcimiaabd0dn0644hnvdta3" equal the hashed NSEC3-owner "cefcsqilefcimiaabd0dn0644hnvdta3" and the hashed NextOwner "fnfabkf6gr4lbq8rm6ndmcncgitcl07l". 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, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner cefcsqilefcimiaabd0dn0644hnvdta3.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



Status: Good. NoData-Proof required and found.

Zone: www.mydomoticz.ovh
www.mydomoticz.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 "6bn2nd5k9nvckpp8hom9dtglvdfbjg1u" between the hashed NSEC3-owner "6bn2nd5k9nvckpp8hom9dtglvdfbjg1u" and the hashed NextOwner "7jk0tlj8meh2bqk0vc3am4uptc6oblqj". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, MX, TXT, RRSIG Validated: RRSIG-Owner 6bn2nd5k9nvckpp8hom9dtglvdfbjg1u.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



RRSIG Type 1 validates the A - Result: 213.186.33.5
Validated: RRSIG-Owner www.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



RRSIG Type 16 validates the TXT - Result: l|fr 3|welcome
Validated: RRSIG-Owner www.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "6bn2nd5k9nvckpp8hom9dtglvdfbjg1u" equal the hashed NSEC3-owner "6bn2nd5k9nvckpp8hom9dtglvdfbjg1u" and the hashed NextOwner "7jk0tlj8meh2bqk0vc3am4uptc6oblqj". 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, MX, TXT, RRSIG Validated: RRSIG-Owner 6bn2nd5k9nvckpp8hom9dtglvdfbjg1u.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "6bn2nd5k9nvckpp8hom9dtglvdfbjg1u" equal the hashed NSEC3-owner "6bn2nd5k9nvckpp8hom9dtglvdfbjg1u" and the hashed NextOwner "7jk0tlj8meh2bqk0vc3am4uptc6oblqj". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, MX, TXT, RRSIG Validated: RRSIG-Owner 6bn2nd5k9nvckpp8hom9dtglvdfbjg1u.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.www.mydomoticz.ovh) sends a valid NSEC3 RR as result with the hashed owner name "6bn2nd5k9nvckpp8hom9dtglvdfbjg1u" (unhashed: www.mydomoticz.ovh). So that's the Closest Encloser of the query name.
Bitmap: A, MX, TXT, RRSIG Validated: RRSIG-Owner 6bn2nd5k9nvckpp8hom9dtglvdfbjg1u.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "61fckrs9u461dmi4jv6kmt3ssck288ro" (unhashed: _tcp.www.mydomoticz.ovh) with the owner "000jdfjp3mlarta733ptcopno2m82mg7" and the NextOwner "6bn2nd5k9nvckpp8hom9dtglvdfbjg1u". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "48ois2opfbgr93bbd31km6196uo3vl0d" (unhashed: *.www.mydomoticz.ovh) with the owner "000jdfjp3mlarta733ptcopno2m82mg7" and the NextOwner "6bn2nd5k9nvckpp8hom9dtglvdfbjg1u". So that NSEC3 confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.www.mydomoticz.ovh) sends a valid NSEC3 RR as result with the hashed query name "2smfof7vorvr7ht2nfp7cs8kp23kotv4" between the hashed NSEC3-owner "000jdfjp3mlarta733ptcopno2m82mg7" and the hashed NextOwner "6bn2nd5k9nvckpp8hom9dtglvdfbjg1u". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: SRV, RRSIG Validated: RRSIG-Owner 000jdfjp3mlarta733ptcopno2m82mg7.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "6bn2nd5k9nvckpp8hom9dtglvdfbjg1u" equal the hashed NSEC3-owner "6bn2nd5k9nvckpp8hom9dtglvdfbjg1u" and the hashed NextOwner "7jk0tlj8meh2bqk0vc3am4uptc6oblqj". 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, MX, TXT, RRSIG Validated: RRSIG-Owner 6bn2nd5k9nvckpp8hom9dtglvdfbjg1u.mydomoticz.ovh., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2022, 02:06:19 +, Signature-Inception: 09.06.2022, 02:06:19 +, KeyTag 4413, Signer-Name: mydomoticz.ovh



Status: Good. NoData-Proof required and found.


3. Name Servers

DomainNameserverNS-IP
www.mydomoticz.ovh
•  dns20.ovh.net
•
mydomoticz.ovh
•  dns20.ovh.net
2001:41d0:1:4a8f::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•

•  ns20.ovh.net
2001:41d0:1:198f::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•
ovh
•  a.nic.fr


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

•  f.ext.nic.fr / s2.bnx
•

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


4. SOA-Entries


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


Domain:ovh
Zone-Name:ovh
Primary:a.nic.fr
Mail:hostmaster.nic.ovh
Serial:2223051012
Refresh:3600
Retry:1800
Expire:3600000
TTL:5400
num Entries:3


Domain:mydomoticz.ovh
Zone-Name:mydomoticz.ovh
Primary:dns20.ovh.net
Mail:tech.ovh.net
Serial:2022060901
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:2


Domain:www.mydomoticz.ovh
Zone-Name:mydomoticz.ovh
Primary:dns20.ovh.net
Mail:tech.ovh.net
Serial:2022060901
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
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://mydomoticz.ovh/
213.186.33.5
302
http://www.mydomoticz.ovh
Html is minified: 111.29 %		0.060

server: nginx
date: Sun, 19 Jun 2022 11:27:49 GMT
content-type: text/html
content-length: 138
location: http://www.mydomoticz.ovh
x-iplb-request-id: 55D702E3:F200_D5BA2105:0050_62AF0837_433D4B2:98B6
x-iplb-instance: 16976
set-cookie: SERVERID77446=200171|Yq8IO|Yq8IO; path=/; HttpOnly
connection: close

• http://www.mydomoticz.ovh/
213.186.33.5 No GZip used - 5911 / 24003 - 24.63 % possible
200

Html is minified: 123.95 %		0.087

server: nginx
date: Sun, 19 Jun 2022 11:27:49 GMT
content-type: text/html; charset=UTF-8
transfer-encoding: chunked
x-iplb-request-id: 55D702E3:F202_D5BA2105:0050_62AF0837_B65BE69:2BF18
x-iplb-instance: 16978
set-cookie: SERVERID77446=200178|Yq8IO|Yq8IO; path=/; HttpOnly
cache-control: private
connection: close

• http://www.mydomoticz.ovh

200

Html is minified: 123.95 %		0.134

server: nginx
date: Sun, 19 Jun 2022 11:27:54 GMT
content-type: text/html; charset=UTF-8
transfer-encoding: chunked
x-iplb-request-id: 55D702E3:F212_D5BA2105:0050_62AF083C_5AD7C1E:98B5
x-iplb-instance: 16976
set-cookie: SERVERID77446=200178|Yq8IP|Yq8IP; path=/; HttpOnly
cache-control: private
connection: close

• https://mydomoticz.ovh/
213.186.33.5
-2

2.174
V
ConnectFailure - Unable to connect to the remote server

• https://www.mydomoticz.ovh/
213.186.33.5
-2

1.080
V
ConnectFailure - Unable to connect to the remote server

• http://mydomoticz.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
213.186.33.5
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		302
http://www.mydomoticz.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 111.29 %		0.077

Visible Content: 302 Found nginx
server: nginx
date: Sun, 19 Jun 2022 11:27:49 GMT
content-type: text/html
content-length: 138
location: http://www.mydomoticz.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
x-iplb-request-id: 55D702E3:F20A_D5BA2105:0050_62AF083B_5CCA76A:25AAA
x-iplb-instance: 16982
set-cookie: SERVERID77446=200172|Yq8IP|Yq8IP; path=/; HttpOnly
connection: close

• http://www.mydomoticz.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
213.186.33.5
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		302
http://www.mydomoticz.ovh
Html is minified: 111.29 %		0.053

Visible Content: 302 Found nginx
server: nginx
date: Sun, 19 Jun 2022 11:27:55 GMT
content-type: text/html
content-length: 138
location: http://www.mydomoticz.ovh
x-iplb-request-id: 55D702E3:F20D_D5BA2105:0050_62AF083B_346B147:98B7
x-iplb-instance: 16976
set-cookie: SERVERID77446=200176|Yq8IP|Yq8IP; path=/; HttpOnly
connection: close

• https://213.186.33.5/
213.186.33.5
-2

1.074
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "mydomoticz.ovh" is domain, 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
Warning: Only one ip address found: mydomoticz.ovh has only one ip address.
Warning: Only one ip address found: www.mydomoticz.ovh 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: mydomoticz.ovh 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.mydomoticz.ovh 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.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
http://mydomoticz.ovh/ 213.186.33.5
302
SERVERID77446=200171|Yq8IO|Yq8IO; path=/; HttpOnly
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.mydomoticz.ovh
200
SERVERID77446=200178|Yq8IP|Yq8IP; path=/; HttpOnly
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.mydomoticz.ovh/ 213.186.33.5
200
SERVERID77446=200178|Yq8IO|Yq8IO; path=/; HttpOnly
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://mydomoticz.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.186.33.5
302
SERVERID77446=200172|Yq8IP|Yq8IP; path=/; HttpOnly
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.mydomoticz.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.186.33.5
302
SERVERID77446=200176|Yq8IP|Yq8IP; path=/; HttpOnly
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
Bhttp://mydomoticz.ovh/ 213.186.33.5
302
SERVERID77446=200171|Yq8IO|Yq8IO; path=/; HttpOnly
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.mydomoticz.ovh
200
SERVERID77446=200178|Yq8IP|Yq8IP; path=/; HttpOnly
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.mydomoticz.ovh/ 213.186.33.5
200
SERVERID77446=200178|Yq8IO|Yq8IO; path=/; HttpOnly
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://mydomoticz.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.186.33.5
302
SERVERID77446=200172|Yq8IP|Yq8IP; path=/; HttpOnly
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.mydomoticz.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.186.33.5
302
SERVERID77446=200176|Yq8IP|Yq8IP; path=/; HttpOnly
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
Chttp://www.mydomoticz.ovh/ 213.186.33.5

http://www.mydomoticz.ovh
Error - redirect destination with a missing / at the end found. So two http status 200 results, only difference: An ending /. Perhaps missing "/" in the redirect rule. May be a problem redirecting folders and files.
HFatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Vhttps://mydomoticz.ovh/ 213.186.33.5
-2

Connect failure - perhaps firewall
Vhttps://www.mydomoticz.ovh/ 213.186.33.5
-2

Connect failure - perhaps firewall
Vhttps://213.186.33.5/ 213.186.33.5
-2

Connect failure - perhaps firewall
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 mydomoticz.ovh, 1 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 www.mydomoticz.ovh, 1 ip addresses.

2. Header-Checks


3. DNS- and NameServer - Checks

AInfo:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 8.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: dns20.ovh.net, ns20.ovh.net, 2 Name Servers included in Delegation: dns20.ovh.net, ns20.ovh.net, 2 Name Servers included in 1 Zone definitions: dns20.ovh.net, ns20.ovh.net, 1 Name Servers listed in SOA.Primary: dns20.ovh.net.
AGood: Only one SOA.Primary Name Server found.: dns20.ovh.net.
AGood: SOA.Primary Name Server included in the delegation set.: dns20.ovh.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: dns20.ovh.net, ns20.ovh.net
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: 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: ovh.net
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: FR
A
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:41d0:, 1 different subnets (first three blocks): 2001:41d0:0001:, 2 different subnets (first four blocks): 2001:41d0:0001:198f:, 2001:41d0:0001:4a8f:
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.
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

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: 48716 milliseconds, 48.716 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Small Code Update - wait one minute


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: dns20.ovh.net, ns20.ovh.net

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

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
dns20.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130
3
ns20.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130
4
dns13.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1
5
ns13.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1
6
ns15.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1
7
dns13.ovh.net: 213.251.188.132
A
dns10.ovh.net (2001:41d0:1:4a81::1)
8
dns13.ovh.net: 2001:41d0:1:4a84::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
9
ns13.ovh.net: 213.251.128.132
A
dns10.ovh.net (2001:41d0:1:4a81::1)
10
ns13.ovh.net: 2001:41d0:1:1984::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
11
ns15.ovh.net: 213.251.128.134
A
dns10.ovh.net (2001:41d0:1:4a81::1)
12
ns15.ovh.net: 2001:41d0:1:1986::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
13
dns20.ovh.net: 213.251.188.143
A
dns10.ovh.net (2001:41d0:1:4a81::1)
14
dns20.ovh.net: 2001:41d0:1:4a8f::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
15
ns20.ovh.net: 213.251.128.143
A
dns10.ovh.net (2001:41d0:1:4a81::1)
16
ns20.ovh.net: 2001:41d0:1:198f::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.mydomoticz.ovh
0

no CAA entry found
1
0
mydomoticz.ovh
0

no CAA entry found
1
0
ovh
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
mydomoticz.ovh
1|www.mydomoticz.ovh
ok
1
0
www.mydomoticz.ovh
3|welcome
ok
1
0
www.mydomoticz.ovh
l|fr
ok
1
0
_acme-challenge.mydomoticz.ovh

Name Error - The domain name does not exist
1
0
_acme-challenge.www.mydomoticz.ovh

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

Name Error - The domain name does not exist
1
0
_acme-challenge.www.mydomoticz.ovh.mydomoticz.ovh

Name Error - The domain name does not exist
1
0
_acme-challenge.www.mydomoticz.ovh.www.mydomoticz.ovh

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

DomainIPPortDescriptionResultAnswer
mydomoticz.ovh
213.186.33.5
21
FTP



mydomoticz.ovh
213.186.33.5
21
FTP



mydomoticz.ovh
213.186.33.5
22
SSH



mydomoticz.ovh
213.186.33.5
22
SSH



mydomoticz.ovh
213.186.33.5
25
SMTP



mydomoticz.ovh
213.186.33.5
25
SMTP



mydomoticz.ovh
213.186.33.5
53
DNS



mydomoticz.ovh
213.186.33.5
53
DNS



mydomoticz.ovh
213.186.33.5
110
POP3



mydomoticz.ovh
213.186.33.5
110
POP3



mydomoticz.ovh
213.186.33.5
143
IMAP



mydomoticz.ovh
213.186.33.5
143
IMAP



mydomoticz.ovh
213.186.33.5
465
SMTP (encrypted)



mydomoticz.ovh
213.186.33.5
465
SMTP (encrypted)



mydomoticz.ovh
213.186.33.5
587
SMTP (encrypted, submission)



mydomoticz.ovh
213.186.33.5
587
SMTP (encrypted, submission)



mydomoticz.ovh
213.186.33.5
993
IMAP (encrypted)



mydomoticz.ovh
213.186.33.5
993
IMAP (encrypted)



mydomoticz.ovh
213.186.33.5
995
POP3 (encrypted)



mydomoticz.ovh
213.186.33.5
995
POP3 (encrypted)



mydomoticz.ovh
213.186.33.5
1433
MS SQL



mydomoticz.ovh
213.186.33.5
1433
MS SQL



mydomoticz.ovh
213.186.33.5
2082
cPanel (http)



mydomoticz.ovh
213.186.33.5
2082
cPanel (http)



mydomoticz.ovh
213.186.33.5
2083
cPanel (https)



mydomoticz.ovh
213.186.33.5
2083
cPanel (https)



mydomoticz.ovh
213.186.33.5
2086
WHM (http)



mydomoticz.ovh
213.186.33.5
2086
WHM (http)



mydomoticz.ovh
213.186.33.5
2087
WHM (https)



mydomoticz.ovh
213.186.33.5
2087
WHM (https)



mydomoticz.ovh
213.186.33.5
2089
cPanel Licensing



mydomoticz.ovh
213.186.33.5
2089
cPanel Licensing



mydomoticz.ovh
213.186.33.5
2095
cPanel Webmail (http)



mydomoticz.ovh
213.186.33.5
2095
cPanel Webmail (http)



mydomoticz.ovh
213.186.33.5
2096
cPanel Webmail (https)



mydomoticz.ovh
213.186.33.5
2096
cPanel Webmail (https)



mydomoticz.ovh
213.186.33.5
2222
DirectAdmin (http)



mydomoticz.ovh
213.186.33.5
2222
DirectAdmin (http)



mydomoticz.ovh
213.186.33.5
2222
DirectAdmin (https)



mydomoticz.ovh
213.186.33.5
2222
DirectAdmin (https)



mydomoticz.ovh
213.186.33.5
3306
mySql



mydomoticz.ovh
213.186.33.5
3306
mySql



mydomoticz.ovh
213.186.33.5
5224
Plesk Licensing



mydomoticz.ovh
213.186.33.5
5224
Plesk Licensing



mydomoticz.ovh
213.186.33.5
5432
PostgreSQL



mydomoticz.ovh
213.186.33.5
5432
PostgreSQL



mydomoticz.ovh
213.186.33.5
8080
Ookla Speedtest (http)



mydomoticz.ovh
213.186.33.5
8080
Ookla Speedtest (http)



mydomoticz.ovh
213.186.33.5
8080
Ookla Speedtest (https)



mydomoticz.ovh
213.186.33.5
8080
Ookla Speedtest (https)



mydomoticz.ovh
213.186.33.5
8083
VestaCP http



mydomoticz.ovh
213.186.33.5
8083
VestaCP http



mydomoticz.ovh
213.186.33.5
8083
VestaCP https



mydomoticz.ovh
213.186.33.5
8083
VestaCP https



mydomoticz.ovh
213.186.33.5
8443
Plesk Administration (https)



mydomoticz.ovh
213.186.33.5
8443
Plesk Administration (https)



mydomoticz.ovh
213.186.33.5
8447
Plesk Installer + Updates



mydomoticz.ovh
213.186.33.5
8447
Plesk Installer + Updates



mydomoticz.ovh
213.186.33.5
8880
Plesk Administration (http)



mydomoticz.ovh
213.186.33.5
8880
Plesk Administration (http)



mydomoticz.ovh
213.186.33.5
10000
Webmin (http)



mydomoticz.ovh
213.186.33.5
10000
Webmin (http)



mydomoticz.ovh
213.186.33.5
10000
Webmin (https)



mydomoticz.ovh
213.186.33.5
10000
Webmin (https)



www.mydomoticz.ovh
213.186.33.5
21
FTP



www.mydomoticz.ovh
213.186.33.5
21
FTP



www.mydomoticz.ovh
213.186.33.5
22
SSH



www.mydomoticz.ovh
213.186.33.5
22
SSH



www.mydomoticz.ovh
213.186.33.5
25
SMTP



www.mydomoticz.ovh
213.186.33.5
25
SMTP



www.mydomoticz.ovh
213.186.33.5
53
DNS



www.mydomoticz.ovh
213.186.33.5
53
DNS



www.mydomoticz.ovh
213.186.33.5
110
POP3



www.mydomoticz.ovh
213.186.33.5
110
POP3



www.mydomoticz.ovh
213.186.33.5
143
IMAP



www.mydomoticz.ovh
213.186.33.5
143
IMAP



www.mydomoticz.ovh
213.186.33.5
465
SMTP (encrypted)



www.mydomoticz.ovh
213.186.33.5
465
SMTP (encrypted)



www.mydomoticz.ovh
213.186.33.5
587
SMTP (encrypted, submission)



www.mydomoticz.ovh
213.186.33.5
587
SMTP (encrypted, submission)



www.mydomoticz.ovh
213.186.33.5
993
IMAP (encrypted)



www.mydomoticz.ovh
213.186.33.5
993
IMAP (encrypted)



www.mydomoticz.ovh
213.186.33.5
995
POP3 (encrypted)



www.mydomoticz.ovh
213.186.33.5
995
POP3 (encrypted)



www.mydomoticz.ovh
213.186.33.5
1433
MS SQL



www.mydomoticz.ovh
213.186.33.5
1433
MS SQL



www.mydomoticz.ovh
213.186.33.5
2082
cPanel (http)



www.mydomoticz.ovh
213.186.33.5
2082
cPanel (http)



www.mydomoticz.ovh
213.186.33.5
2083
cPanel (https)



www.mydomoticz.ovh
213.186.33.5
2083
cPanel (https)



www.mydomoticz.ovh
213.186.33.5
2086
WHM (http)



www.mydomoticz.ovh
213.186.33.5
2086
WHM (http)



www.mydomoticz.ovh
213.186.33.5
2087
WHM (https)



www.mydomoticz.ovh
213.186.33.5
2087
WHM (https)



www.mydomoticz.ovh
213.186.33.5
2089
cPanel Licensing



www.mydomoticz.ovh
213.186.33.5
2089
cPanel Licensing



www.mydomoticz.ovh
213.186.33.5
2095
cPanel Webmail (http)



www.mydomoticz.ovh
213.186.33.5
2095
cPanel Webmail (http)



www.mydomoticz.ovh
213.186.33.5
2096
cPanel Webmail (https)



www.mydomoticz.ovh
213.186.33.5
2096
cPanel Webmail (https)



www.mydomoticz.ovh
213.186.33.5
2222
DirectAdmin (http)



www.mydomoticz.ovh
213.186.33.5
2222
DirectAdmin (http)



www.mydomoticz.ovh
213.186.33.5
2222
DirectAdmin (https)



www.mydomoticz.ovh
213.186.33.5
2222
DirectAdmin (https)



www.mydomoticz.ovh
213.186.33.5
3306
mySql



www.mydomoticz.ovh
213.186.33.5
3306
mySql



www.mydomoticz.ovh
213.186.33.5
5224
Plesk Licensing



www.mydomoticz.ovh
213.186.33.5
5224
Plesk Licensing



www.mydomoticz.ovh
213.186.33.5
5432
PostgreSQL



www.mydomoticz.ovh
213.186.33.5
5432
PostgreSQL



www.mydomoticz.ovh
213.186.33.5
8080
Ookla Speedtest (http)



www.mydomoticz.ovh
213.186.33.5
8080
Ookla Speedtest (http)



www.mydomoticz.ovh
213.186.33.5
8080
Ookla Speedtest (https)



www.mydomoticz.ovh
213.186.33.5
8080
Ookla Speedtest (https)



www.mydomoticz.ovh
213.186.33.5
8083
VestaCP http



www.mydomoticz.ovh
213.186.33.5
8083
VestaCP http



www.mydomoticz.ovh
213.186.33.5
8083
VestaCP https



www.mydomoticz.ovh
213.186.33.5
8083
VestaCP https



www.mydomoticz.ovh
213.186.33.5
8443
Plesk Administration (https)



www.mydomoticz.ovh
213.186.33.5
8443
Plesk Administration (https)



www.mydomoticz.ovh
213.186.33.5
8447
Plesk Installer + Updates



www.mydomoticz.ovh
213.186.33.5
8447
Plesk Installer + Updates



www.mydomoticz.ovh
213.186.33.5
8880
Plesk Administration (http)



www.mydomoticz.ovh
213.186.33.5
8880
Plesk Administration (http)



www.mydomoticz.ovh
213.186.33.5
10000
Webmin (http)



www.mydomoticz.ovh
213.186.33.5
10000
Webmin (http)



www.mydomoticz.ovh
213.186.33.5
10000
Webmin (https)



www.mydomoticz.ovh
213.186.33.5
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=c66ca71b-bfa4-4ca9-9131-2d7d645db04f


Last Result: https://check-your-website.server-daten.de/?q=mydomoticz.ovh - 2023-08-21 20:54:07


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

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

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


Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions