W

wrong Web-Response

Checked:
13.08.2019 11:18:57


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
iampac.de
A
134.209.227.186
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC
No Hostname found
yes
1
0

AAAA

yes


www.iampac.de
A
134.209.227.186
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC
No Hostname found
yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)
(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 59944, Flags 256

1 RRSIG RR to validate DNSKEY RR found

Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 31.08.2019, 00:00:00, Signature-Inception: 10.08.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
de
1 DS RR in the parent zone found

1 RRSIG RR to validate DS RR found

Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.08.2019, 05:00:00, Signature-Inception: 13.08.2019, 04:00:00, KeyTag 59944, Signer-Name: (root)

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

3 DNSKEY RR found

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

Public Key with Algorithm 8, KeyTag 43128, Flags 256

Public Key with Algorithm 8, KeyTag 47740, Flags 256

1 RRSIG RR to validate DNSKEY RR found

Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 29.08.2019, 12:00:00, Signature-Inception: 08.08.2019, 12:00:00, KeyTag 39227, Signer-Name: de

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

Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 39227, DigestType 2 and Digest "qrcwg7nvcOSl6UdppBisEuiH/DwIde8gbDRR3EC2xPo=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
iampac.de
0 DS RR in the parent zone found

DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.

0 DNSKEY RR found


www.iampac.de
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.iampac.de
  ns1.digitalocean.com / 67m5

iampac.de
  ns1.digitalocean.com / 67m26
173.245.58.51
Ashburn/Virginia/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::adf5:3a33
Columbus/North Carolina/United States (US) - CLOUDFLARE


  ns2.digitalocean.com / 67m25
173.245.59.41
Ashburn/Virginia/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::adf5:3b29
Columbus/North Carolina/United States (US) - CLOUDFLARE


  ns3.digitalocean.com / 67m4
198.41.222.173
Ashburn/Virginia/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::c629:dead
Columbus/North Carolina/United States (US) - CLOUDFLARE

de
  a.nic.de / ns-1.de.de8.bind


  f.nic.de / ns-2.de.de1.bind


  l.de.net / ns-1.de.fr1.bind


  n.de.net / s3.amx


  s.de.net / ns-2.de.de9.bind


  z.nic.de / ns-1.de.de8.bind


4. SOA-Entries


Domain:de
Primary:f.nic.de
Mail:its.denic.de
Serial:2019081341
Refresh:7200
Retry:7200
Expire:3600000
TTL:7200
num Entries:6


Domain:iampac.de
Primary:ns1.digitalocean.com
Mail:hostmaster.iampac.de
Serial:1565685787
Refresh:10800
Retry:3600
Expire:604800
TTL:1800
num Entries:6


Domain:www.iampac.de
Primary:ns1.digitalocean.com
Mail:hostmaster.iampac.de
Serial:1565685787
Refresh:10800
Retry:3600
Expire:604800
TTL:1800
num Entries:1


5. Url-Checks


show header:
Domainname Http-StatusredirectSec.G
• http://iampac.de/
134.209.227.186
200

0.043
H
small content:
<!DOCTYPE HTML> <html> <head> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <meta http-equiv='Content-Type' content='text/html;charset=UTF-8'/> <title>Mobile App with data-bound List</title> <script src="https://sapui5.hana.ondemand.com/resources/sap-ui-core.js" id="sap-ui-bootstrap" data-sap-ui-libs="sap.m,sap.ui.layout" data-sap-ui-xx-bindingSyntax="complex" data-sap-ui-theme="sap_bluecrystal"></script> <!-- load the mobile lib "sap.m", the layout lib and the "sap_bluecrystal" theme --> <script type="text/javascript"> // create the data // create some dummy JSON data var data = { names: [ {firstName: "Peter", lastName: "Mueller"}, {firstName: "Petra", lastName: "Maier"}, {firstName: "Thomas", lastName: "Smith"}, {firstName: "John", lastName: "Williams"}, {firstName: "Maria", lastName: "Jones"} ] }; // create a Model with this data var model = new sap.ui.model.json.JSONModel(); model.setData(data); // create the UI // create a List control var list = new sap.m.List({ headerText:"Names" }); // bind the List items to the data collection list.bindItems({ path : "/names", sorter : new sap.ui.model.Sorter("lastName"), template : new sap.m.StandardListItem({ title: "{lastName}", description: "{firstName}", type: sap.m.ListType.Navigation, press:function(evt){ var oBindingContext = evt.getSource().getBindingContext(); // evt.getSource() is the ListItem page2.setBindingContext(oBindingContext); // make sure the detail page has the correct data context app.to("page2"); } }) }); // create the page holding the List var page1 = new sap.m.Page({ title: "List Page", content : list }); // create the detail page var page2 = new sap.m.Page("page2", { title: "Detail Page", showNavButton: true, navButtonPress: function(){ app.back(); }, content : [ new sap.ui.layout.form.SimpleForm({ title: "Details for {firstName} {lastName}", content: [ new sap.m.Label({text: "First Name"}), new sap.m.Text({text: "{firstName}"}), new sap.m.Label({text: "Last Name"}), new sap.m.Text({text: "{lastName}"}) ] }) ] }); // create a mobile App holding the pages and place the App into the HTML document var app = new sap.m.App({ pages: [page1, page2] }).placeAt("content"); // set the model to the App; it will be propagated to the children app.setModel(model); </script> </head> <body id="content" class="sapUiBody"> </body> </html>
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 13 Aug 2019 09:19:23 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 2660
Connection: close
X-Frame-Options: SAMEORIGIN

• http://www.iampac.de/
134.209.227.186
200

0.050
H
small content:
<!DOCTYPE HTML> <html> <head> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <meta http-equiv='Content-Type' content='text/html;charset=UTF-8'/> <title>Mobile App with data-bound List</title> <script src="https://sapui5.hana.ondemand.com/resources/sap-ui-core.js" id="sap-ui-bootstrap" data-sap-ui-libs="sap.m,sap.ui.layout" data-sap-ui-xx-bindingSyntax="complex" data-sap-ui-theme="sap_bluecrystal"></script> <!-- load the mobile lib "sap.m", the layout lib and the "sap_bluecrystal" theme --> <script type="text/javascript"> // create the data // create some dummy JSON data var data = { names: [ {firstName: "Peter", lastName: "Mueller"}, {firstName: "Petra", lastName: "Maier"}, {firstName: "Thomas", lastName: "Smith"}, {firstName: "John", lastName: "Williams"}, {firstName: "Maria", lastName: "Jones"} ] }; // create a Model with this data var model = new sap.ui.model.json.JSONModel(); model.setData(data); // create the UI // create a List control var list = new sap.m.List({ headerText:"Names" }); // bind the List items to the data collection list.bindItems({ path : "/names", sorter : new sap.ui.model.Sorter("lastName"), template : new sap.m.StandardListItem({ title: "{lastName}", description: "{firstName}", type: sap.m.ListType.Navigation, press:function(evt){ var oBindingContext = evt.getSource().getBindingContext(); // evt.getSource() is the ListItem page2.setBindingContext(oBindingContext); // make sure the detail page has the correct data context app.to("page2"); } }) }); // create the page holding the List var page1 = new sap.m.Page({ title: "List Page", content : list }); // create the detail page var page2 = new sap.m.Page("page2", { title: "Detail Page", showNavButton: true, navButtonPress: function(){ app.back(); }, content : [ new sap.ui.layout.form.SimpleForm({ title: "Details for {firstName} {lastName}", content: [ new sap.m.Label({text: "First Name"}), new sap.m.Text({text: "{firstName}"}), new sap.m.Label({text: "Last Name"}), new sap.m.Text({text: "{lastName}"}) ] }) ] }); // create a mobile App holding the pages and place the App into the HTML document var app = new sap.m.App({ pages: [page1, page2] }).placeAt("content"); // set the model to the App; it will be propagated to the children app.setModel(model); </script> </head> <body id="content" class="sapUiBody"> </body> </html>
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 13 Aug 2019 09:19:23 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 2660
Connection: close
X-Frame-Options: SAMEORIGIN

• https://iampac.de/
134.209.227.186
-4

0.084
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. The handshake failed due to an unexpected packet format.

• https://www.iampac.de/
134.209.227.186
-4

0.087
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. The handshake failed due to an unexpected packet format.

• http://iampac.de:443/
134.209.227.186
-11

0.046
A
ServerProtocolViolation - The server committed a protocol violation. Section=ResponseStatusLine
Visible Content:

• http://www.iampac.de:443/
134.209.227.186
-11

0.043
A
ServerProtocolViolation - The server committed a protocol violation. Section=ResponseStatusLine
Visible Content:

• http://iampac.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
134.209.227.186
404

0.050
A
Not Found
Visible Content: Page not found (404) Request Method: GET Request URL: http://iampac.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Using the URLconf defined in Dex.urls , Django tried these URL patterns, in this order: admin/ The current path, .well-known/acme-challenge/check-your-website-dot-server-daten-dot-de , didn't match any of these. You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False , and Django will display a standard 404 page.
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 13 Aug 2019 09:19:23 GMT
Content-Type: text/html
Content-Length: 2238
Connection: close
X-Frame-Options: SAMEORIGIN

• http://www.iampac.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
134.209.227.186
404

0.044
A
Not Found
Visible Content: Page not found (404) Request Method: GET Request URL: http://www.iampac.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Using the URLconf defined in Dex.urls , Django tried these URL patterns, in this order: admin/ The current path, .well-known/acme-challenge/check-your-website-dot-server-daten-dot-de , didn't match any of these. You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False , and Django will display a standard 404 page.
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 13 Aug 2019 09:19:23 GMT
Content-Type: text/html
Content-Length: 2242
Connection: close
X-Frame-Options: SAMEORIGIN

6. Comments

Aname "iampac.de" is domain, public suffix is "de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (4 urls)
http://iampac.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 134.209.227.186


Url with incomplete Content-Type - header - missing charset
http://www.iampac.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 134.209.227.186


Url with incomplete Content-Type - header - missing charset
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.
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.
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
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
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, there must be a certificate. But the certificate may be expired or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors.
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: 33096 milliseconds, 33.096 seconds


7. Connections

No connection informations found. Perhaps only http - connections.


8. Certificates

No certificate informations found. Perhaps only http - connections.


9. Last Certificates - Certificate Transparency Log Check (BETA)

1. Source CertSpotter - active certificates

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow.

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
1
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1767043801
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-08-13 06:07:21
2019-11-11 07:07:21
iampac.de, www.iampac.de
2 entries
duplicate nr. 1


10. Html-Content - Entries (BETA - mixed content and other checks)

No Html-Content entries found. Only checked if https + status 200/401/403/404


11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.iampac.de
0

no CAA entry found
1
0
iampac.de
0

no CAA entry found
1
0
de
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
iampac.de

ok
1
0
www.iampac.de

ok
1
0
_acme-challenge.iampac.de

Name Error - The domain name does not exist
1
0
_acme-challenge.www.iampac.de

Name Error - The domain name does not exist
1
0
_acme-challenge.iampac.de.iampac.de

Name Error - The domain name does not exist
1
0
_acme-challenge.www.iampac.de.iampac.de

Name Error - The domain name does not exist
1
0
_acme-challenge.www.iampac.de.www.iampac.de

Name Error - The domain name does not exist
1
0


13. Portchecks (BETA)

Domain or IPPortDescriptionResultAnswer
iampac.de
21
FTP



iampac.de
21
FTP



iampac.de
22
SSH



iampac.de
22
SSH



iampac.de
25
SMTP



iampac.de
25
SMTP



iampac.de
53
DNS



iampac.de
53
DNS



iampac.de
110
POP3



iampac.de
110
POP3



iampac.de
143
IMAP



iampac.de
143
IMAP



iampac.de
465
SMTP (encrypted)



iampac.de
465
SMTP (encrypted)



iampac.de
587
SMTP (encrypted, submission)



iampac.de
587
SMTP (encrypted, submission)



iampac.de
993
IMAP (encrypted)



iampac.de
993
IMAP (encrypted)



iampac.de
995
POP3 (encrypted)



iampac.de
995
POP3 (encrypted)



iampac.de
1433
MS SQL



iampac.de
1433
MS SQL



iampac.de
2082
cPanel (http)



iampac.de
2082
cPanel (http)



iampac.de
2083
cPanel (https)



iampac.de
2083
cPanel (https)



iampac.de
2086
WHM (http)



iampac.de
2086
WHM (http)



iampac.de
2087
WHM SSL



iampac.de
2087
WHM SSL



iampac.de
2089
cPanel Licensing



iampac.de
2089
cPanel Licensing



iampac.de
2095
cPanel Webmail (http)



iampac.de
2095
cPanel Webmail (http)



iampac.de
2096
cPanel Webmail (https)



iampac.de
2096
cPanel Webmail (https)



iampac.de
3306
mySql



iampac.de
3306
mySql



iampac.de
5224
Plesk Licensing



iampac.de
5224
Plesk Licensing



iampac.de
5432
PostgreSQL



iampac.de
5432
PostgreSQL



iampac.de
8080
Ookla Speedtest (http)



iampac.de
8080
Ookla Speedtest (http)



iampac.de
8080
Ookla Speedtest (https)



iampac.de
8080
Ookla Speedtest (https)



iampac.de
8083
VestaCP http



iampac.de
8083
VestaCP http



iampac.de
8083
VestaCP https



iampac.de
8083
VestaCP https



iampac.de
8443
Plesk Administration (https)



iampac.de
8443
Plesk Administration (https)



iampac.de
8447
Plesk Installer + Updates



iampac.de
8447
Plesk Installer + Updates



iampac.de
8880
Plesk Administration (http)



iampac.de
8880
Plesk Administration (http)



iampac.de
10000
Webmin (http)



iampac.de
10000
Webmin (http)



iampac.de
10000
Webmin (https)



iampac.de
10000
Webmin (https)



www.iampac.de
21
FTP



www.iampac.de
21
FTP



www.iampac.de
22
SSH



www.iampac.de
22
SSH



www.iampac.de
25
SMTP



www.iampac.de
25
SMTP



www.iampac.de
53
DNS



www.iampac.de
53
DNS



www.iampac.de
110
POP3



www.iampac.de
110
POP3



www.iampac.de
143
IMAP



www.iampac.de
143
IMAP



www.iampac.de
465
SMTP (encrypted)



www.iampac.de
465
SMTP (encrypted)



www.iampac.de
587
SMTP (encrypted, submission)



www.iampac.de
587
SMTP (encrypted, submission)



www.iampac.de
993
IMAP (encrypted)



www.iampac.de
993
IMAP (encrypted)



www.iampac.de
995
POP3 (encrypted)



www.iampac.de
995
POP3 (encrypted)



www.iampac.de
1433
MS SQL



www.iampac.de
1433
MS SQL



www.iampac.de
2082
cPanel (http)



www.iampac.de
2082
cPanel (http)



www.iampac.de
2083
cPanel (https)



www.iampac.de
2083
cPanel (https)



www.iampac.de
2086
WHM (http)



www.iampac.de
2086
WHM (http)



www.iampac.de
2087
WHM SSL



www.iampac.de
2087
WHM SSL



www.iampac.de
2089
cPanel Licensing



www.iampac.de
2089
cPanel Licensing



www.iampac.de
2095
cPanel Webmail (http)



www.iampac.de
2095
cPanel Webmail (http)



www.iampac.de
2096
cPanel Webmail (https)



www.iampac.de
2096
cPanel Webmail (https)



www.iampac.de
3306
mySql



www.iampac.de
3306
mySql



www.iampac.de
5224
Plesk Licensing



www.iampac.de
5224
Plesk Licensing



www.iampac.de
5432
PostgreSQL



www.iampac.de
5432
PostgreSQL



www.iampac.de
8080
Ookla Speedtest (http)



www.iampac.de
8080
Ookla Speedtest (http)



www.iampac.de
8080
Ookla Speedtest (https)



www.iampac.de
8080
Ookla Speedtest (https)



www.iampac.de
8083
VestaCP http



www.iampac.de
8083
VestaCP http



www.iampac.de
8083
VestaCP https



www.iampac.de
8083
VestaCP https



www.iampac.de
8443
Plesk Administration (https)



www.iampac.de
8443
Plesk Administration (https)



www.iampac.de
8447
Plesk Installer + Updates



www.iampac.de
8447
Plesk Installer + Updates



www.iampac.de
8880
Plesk Administration (http)



www.iampac.de
8880
Plesk Administration (http)



www.iampac.de
10000
Webmin (http)



www.iampac.de
10000
Webmin (http)



www.iampac.de
10000
Webmin (https)



www.iampac.de
10000
Webmin (https)



134.209.227.186
21
FTP



134.209.227.186
21
FTP



134.209.227.186
22
SSH



134.209.227.186
22
SSH



134.209.227.186
25
SMTP



134.209.227.186
25
SMTP



134.209.227.186
53
DNS



134.209.227.186
53
DNS



134.209.227.186
110
POP3



134.209.227.186
110
POP3



134.209.227.186
143
IMAP



134.209.227.186
143
IMAP



134.209.227.186
465
SMTP (encrypted)



134.209.227.186
465
SMTP (encrypted)



134.209.227.186
587
SMTP (encrypted, submission)



134.209.227.186
587
SMTP (encrypted, submission)



134.209.227.186
993
IMAP (encrypted)



134.209.227.186
993
IMAP (encrypted)



134.209.227.186
995
POP3 (encrypted)



134.209.227.186
995
POP3 (encrypted)



134.209.227.186
1433
MS SQL



134.209.227.186
1433
MS SQL



134.209.227.186
2082
cPanel (http)



134.209.227.186
2082
cPanel (http)



134.209.227.186
2083
cPanel (https)



134.209.227.186
2083
cPanel (https)



134.209.227.186
2086
WHM (http)



134.209.227.186
2086
WHM (http)



134.209.227.186
2087
WHM SSL



134.209.227.186
2087
WHM SSL



134.209.227.186
2089
cPanel Licensing



134.209.227.186
2089
cPanel Licensing



134.209.227.186
2095
cPanel Webmail (http)



134.209.227.186
2095
cPanel Webmail (http)



134.209.227.186
2096
cPanel Webmail (https)



134.209.227.186
2096
cPanel Webmail (https)



134.209.227.186
3306
mySql



134.209.227.186
3306
mySql



134.209.227.186
5224
Plesk Licensing



134.209.227.186
5224
Plesk Licensing



134.209.227.186
5432
PostgreSQL



134.209.227.186
5432
PostgreSQL



134.209.227.186
8080
Ookla Speedtest (http)



134.209.227.186
8080
Ookla Speedtest (http)



134.209.227.186
8080
Ookla Speedtest (https)



134.209.227.186
8080
Ookla Speedtest (https)



134.209.227.186
8083
VestaCP http



134.209.227.186
8083
VestaCP http



134.209.227.186
8083
VestaCP https



134.209.227.186
8083
VestaCP https



134.209.227.186
8443
Plesk Administration (https)



134.209.227.186
8443
Plesk Administration (https)



134.209.227.186
8447
Plesk Installer + Updates



134.209.227.186
8447
Plesk Installer + Updates



134.209.227.186
8880
Plesk Administration (http)



134.209.227.186
8880
Plesk Administration (http)



134.209.227.186
10000
Webmin (http)



134.209.227.186
10000
Webmin (http)



134.209.227.186
10000
Webmin (https)



134.209.227.186
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=e883db6f-99d7-40d9-829b-2e799162b506


Last Result: https://check-your-website.server-daten.de/?q=iampac.de - 2019-08-13 11:18:57


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

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