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

0 in Queue, 0 of max. 4 Checks (12:17:15)
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. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

A+

 

Top configuration, no warnings +Preload

 

Checked:
06.12.2019 05:41:04

 

Older results

 

A+ - 05.12.2019 11:22:06
H - 05.12.2019 11:20:04
A+ - 28.10.2019 22:22:20
A+ - 28.10.2019 21:07:54
A+ - 28.10.2019 20:43:12
A+ - 28.10.2019 05:24:23
I - 28.10.2019 01:07:46
H - 08.10.2019 22:13:35

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
photo.omshivalab.com
CNAME
omshivalab.com
yes
1
0

A
69.172.185.185
Vancouver/British Columbia/Canada (CA) - TekSavvy Solutions, Inc.
Hostname: mail.omshivalab.com
yes


www.photo.omshivalab.com

Name Error
yes
1
0

 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






• 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 22545, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.12.2019, 00:00:00 +, Signature-Inception: 30.11.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)






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






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



Zone: com

com
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 18.12.2019, 17:00:00 +, Signature-Inception: 05.12.2019, 16:00:00 +, KeyTag 22545, Signer-Name: (root)






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






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 12163, Flags 256






Public Key with Algorithm 8, KeyTag 17708, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.12.2019, 19:24:21 +, Signature-Inception: 27.11.2019, 19:19:21 +, KeyTag 30909, Signer-Name: com






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.12.2019, 19:24:21 +, Signature-Inception: 27.11.2019, 19:19:21 +, KeyTag 30909, Signer-Name: com






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






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






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



Zone: omshivalab.com

omshivalab.com
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner omshivalab.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 09.12.2019, 06:59:15 +, Signature-Inception: 02.12.2019, 05:49:15 +, KeyTag 12163, Signer-Name: com






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 32779, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner omshivalab.com., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 25.12.2019, 21:56:35 +, Signature-Inception: 03.12.2019, 21:56:35 +, KeyTag 17711, Signer-Name: omshivalab.com






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






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



Zone: photo.omshivalab.com

photo.omshivalab.com
0 DS RR in the parent zone found



Zone: www.photo.omshivalab.com

www.photo.omshivalab.com
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "1pu92o4shjpa5bjfp2fkg0eoks5f6q5p" between the hashed NSEC3-owner "0f2sdtmmu0n88q4hfblvusok7utp3o5c" and the hashed NextOwner "2213ucdnrhv2cfpsa2cr99ogsuuolge8". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: TXT, RRSIG Validated: RRSIG-Owner 0f2sdtmmu0n88q4hfblvusok7utp3o5c.omshivalab.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 25.12.2019, 21:56:35 +, Signature-Inception: 03.12.2019, 21:56:35 +, KeyTag 32779, Signer-Name: omshivalab.com

 

3. Name Servers

DomainNameserverNS-IP
www.photo.omshivalab.com
•  ns-cloud-c1.googledomains.com

omshivalab.com
•  ns-cloud-c1.googledomains.com
•

•  ns-cloud-c2.googledomains.com
•

•  ns-cloud-c3.googledomains.com
•

•  ns-cloud-c4.googledomains.com
•
com
•  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
•

 

4. SOA-Entries


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


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


Domain:omshivalab.com
Zone-Name:
Primary:ns-cloud-c1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:237
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:4


Domain:www.photo.omshivalab.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

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

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://photo.omshivalab.com/
69.172.185.185
301
https://photo.omshivalab.com/
Html is minified: 100.00 %
0.363
A
Date: Fri, 06 Dec 2019 04:41:22 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 237
Connection: close
Content-Security-Policy: upgrade-insecure-requests
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer-when-downgrade
Expect-CT: max-age=7776000, enforce
X-Frame-Options: sameorigin
Location: https://photo.omshivalab.com/

• https://photo.omshivalab.com/
69.172.185.185
Inline-JavaScript (∑/total): 24/16938 Inline-CSS (∑/total): 9/61651		200

Html is minified: 693.13 %
Other inline scripts (∑/total): 24/16938		4.990
A
small visible content (num chars: 198)
photo.omshivalab.com Blog Home / Blog 2019-10-01 by Administrator Uncategorized 1 comment Hello world! Welcome to WordPress. This is your first post. Edit or delete it, then start writing! Read More
Date: Fri, 06 Dec 2019 04:41:22 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 20616
Connection: close
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
Content-Security-Policy: upgrade-insecure-requests
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer-when-downgrade
Expect-CT: max-age=7776000, enforce
X-Frame-Options: sameorigin
Last-Modified: Fri, 06 Dec 2019 03:15:20 GMT
Vary: Accept-Encoding
Content-Encoding: gzip

• http://photo.omshivalab.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
69.172.185.185
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 110.61 %
Other inline scripts (∑/total): 0/0		0.360
A
Not Found
Visible Content: 404 Not Found nginx
Date: Fri, 06 Dec 2019 04:41:27 GMT
Content-Type: text/html
Content-Length: 146
Connection: close

 

7. Comments


1. General Results, most used to calculate the result

Aname "photo.omshivalab.com" is subdomain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
AGood: All ip addresses are public 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
AGood: every https has a Strict Transport Security Header
AGood: HSTS max-age is long enough, 63072000 seconds = 730 days
AGood: HSTS has includeSubdomains - directive
AGood: HSTS has preload directive
AExcellent: Main Domain is in the Google-Preload-List
AExcellent: Main Domain is in the Mozilla/Firefox-Preload-List
AHSTS-Preload-Status: Preloaded. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (2 urls)
http://photo.omshivalab.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.172.185.185


Url with incomplete Content-Type - header - missing charset
Ahttp://photo.omshivalab.com/ 69.172.185.185
301
https://photo.omshivalab.com/
Correct redirect http - https with the same domain name

2. Header-Checks


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns-cloud-c1.googledomains.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.
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

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
https://photo.omshivalab.com/ 69.172.185.185
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://photo.omshivalab.com/ 69.172.185.185
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.
Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 1 external CSS / JavaScript files without GZip found - 35 with GZip, 36 complete
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 external CSS / JavaScript files without Cache-Control-Header, 35 with Cache-Control, but no max-age, 1 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 36 complete.
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: 69284 milliseconds, 69.284 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
photo.omshivalab.com
69.172.185.185
443
ok
Tls12
ECDH Ephermal
256
Aes128
128
Sha256
error checking OCSP stapling
ok
photo.omshivalab.com
69.172.185.185
443
ok
Tls12

ECDH Ephermal
256
Aes128
128
Sha256
error checking OCSP stapling
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
 Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - duplicate certificates

1CN=*.omshivalab.com


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


3CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

 

9. Certificates

1.
1.
CN=*.omshivalab.com
06.12.2019
05.03.2020
2321 days expired		*.omshivalab.com - 1 entry
1.
1.
CN=*.omshivalab.com
06.12.2019

05.03.2020
2321 days expired


*.omshivalab.com - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:030F1122AECD95738530BB1D9905C7FF811E
Thumbprint:64F08335B6D33896DFA35879109ABAE4B05D962F
SHA256 / Certificate:ddOosxuhDSWQ5u39qo/6uDSCxaKcfHSSko22OZy1kOM=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):7406ebd32be74b4bd91567917f87924032b57b44a35d1fed688495daa8b90747
SHA256 hex / Subject Public Key Information (SPKI):7406ebd32be74b4bd91567917f87924032b57b44a35d1fed688495daa8b90747
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
1944 days expired

2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
1944 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
1747 days expired

3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
1747 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
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)

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

Summary

No data found or small Code-update

 

Details (currently limited to 500 rows - some problems with spam users)

Small Code Update - wait one minute

 

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

 

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
photo.omshivalab.com



1
0
omshivalab.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
omshivalab.com
google-site-verification=bVctXo-D96kLhIbjPBT8eEUoMqZGc34uQ3gxhg6BJ8Y
ok
1
0
omshivalab.com
v=spf1 mx a include:_spf.google.com ip4:69.172.185.185/32 -all
ok
1
0
omshivalab.com
yandex-verification: 5f8f467ea254539d
ok
1
0
photo.omshivalab.com
google-site-verification=bVctXo-D96kLhIbjPBT8eEUoMqZGc34uQ3gxhg6BJ8Y
ok
1
0
photo.omshivalab.com
v=spf1 mx a include:_spf.google.com ip4:69.172.185.185/32 -all
ok
1
0
photo.omshivalab.com
yandex-verification: 5f8f467ea254539d
ok
1
0
_acme-challenge.photo.omshivalab.com

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

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

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

DomainIPPortDescriptionResultAnswer
photo.omshivalab.com
69.172.185.185
21
FTP



photo.omshivalab.com
69.172.185.185
21
FTP



photo.omshivalab.com
69.172.185.185
22
SSH



photo.omshivalab.com
69.172.185.185
22
SSH



photo.omshivalab.com
69.172.185.185
25
SMTP



photo.omshivalab.com
69.172.185.185
25
SMTP



photo.omshivalab.com
69.172.185.185
53
DNS



photo.omshivalab.com
69.172.185.185
53
DNS



photo.omshivalab.com
69.172.185.185
110
POP3



photo.omshivalab.com
69.172.185.185
110
POP3



photo.omshivalab.com
69.172.185.185
143
IMAP



photo.omshivalab.com
69.172.185.185
143
IMAP



photo.omshivalab.com
69.172.185.185
465
SMTP (encrypted)



photo.omshivalab.com
69.172.185.185
465
SMTP (encrypted)



photo.omshivalab.com
69.172.185.185
587
SMTP (encrypted, submission)



photo.omshivalab.com
69.172.185.185
587
SMTP (encrypted, submission)



photo.omshivalab.com
69.172.185.185
993
IMAP (encrypted)



photo.omshivalab.com
69.172.185.185
993
IMAP (encrypted)



photo.omshivalab.com
69.172.185.185
995
POP3 (encrypted)



photo.omshivalab.com
69.172.185.185
995
POP3 (encrypted)



photo.omshivalab.com
69.172.185.185
1433
MS SQL



photo.omshivalab.com
69.172.185.185
1433
MS SQL



photo.omshivalab.com
69.172.185.185
2082
cPanel (http)



photo.omshivalab.com
69.172.185.185
2082
cPanel (http)



photo.omshivalab.com
69.172.185.185
2083
cPanel (https)



photo.omshivalab.com
69.172.185.185
2083
cPanel (https)



photo.omshivalab.com
69.172.185.185
2086
WHM (http)



photo.omshivalab.com
69.172.185.185
2086
WHM (http)



photo.omshivalab.com
69.172.185.185
2087
WHM (https)



photo.omshivalab.com
69.172.185.185
2087
WHM (https)



photo.omshivalab.com
69.172.185.185
2089
cPanel Licensing



photo.omshivalab.com
69.172.185.185
2089
cPanel Licensing



photo.omshivalab.com
69.172.185.185
2095
cPanel Webmail (http)



photo.omshivalab.com
69.172.185.185
2095
cPanel Webmail (http)



photo.omshivalab.com
69.172.185.185
2096
cPanel Webmail (https)



photo.omshivalab.com
69.172.185.185
2096
cPanel Webmail (https)



photo.omshivalab.com
69.172.185.185
2222
DirectAdmin (http)



photo.omshivalab.com
69.172.185.185
2222
DirectAdmin (http)



photo.omshivalab.com
69.172.185.185
2222
DirectAdmin (https)



photo.omshivalab.com
69.172.185.185
2222
DirectAdmin (https)



photo.omshivalab.com
69.172.185.185
3306
mySql



photo.omshivalab.com
69.172.185.185
3306
mySql



photo.omshivalab.com
69.172.185.185
5224
Plesk Licensing



photo.omshivalab.com
69.172.185.185
5224
Plesk Licensing



photo.omshivalab.com
69.172.185.185
5432
PostgreSQL



photo.omshivalab.com
69.172.185.185
5432
PostgreSQL



photo.omshivalab.com
69.172.185.185
8080
Ookla Speedtest (http)



photo.omshivalab.com
69.172.185.185
8080
Ookla Speedtest (http)



photo.omshivalab.com
69.172.185.185
8080
Ookla Speedtest (https)



photo.omshivalab.com
69.172.185.185
8080
Ookla Speedtest (https)



photo.omshivalab.com
69.172.185.185
8083
VestaCP http



photo.omshivalab.com
69.172.185.185
8083
VestaCP http



photo.omshivalab.com
69.172.185.185
8083
VestaCP https



photo.omshivalab.com
69.172.185.185
8083
VestaCP https



photo.omshivalab.com
69.172.185.185
8443
Plesk Administration (https)



photo.omshivalab.com
69.172.185.185
8443
Plesk Administration (https)



photo.omshivalab.com
69.172.185.185
8447
Plesk Installer + Updates



photo.omshivalab.com
69.172.185.185
8447
Plesk Installer + Updates



photo.omshivalab.com
69.172.185.185
8880
Plesk Administration (http)



photo.omshivalab.com
69.172.185.185
8880
Plesk Administration (http)



photo.omshivalab.com
69.172.185.185
10000
Webmin (http)



photo.omshivalab.com
69.172.185.185
10000
Webmin (http)



photo.omshivalab.com
69.172.185.185
10000
Webmin (https)



photo.omshivalab.com
69.172.185.185
10000
Webmin (https)



 

 

Permalink: https://check-your-website.server-daten.de/?i=e608d207-7c98-4df6-867a-155f01417e97

 

Last Result: https://check-your-website.server-daten.de/?q=photo.omshivalab.com - 2019-12-06 05:41:04

 

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

 

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

 

 

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

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=photo.omshivalab.com

 

 

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