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


Info: Problems with 3.048.289 Letsencrypt certificates (378.325 accounts). They must be revoked (revocation starts 2020-03-04 20:00 UTC) - see Revoking certain certificates on March 4. Update 2020-03-07: Good news: Mass-revocation is canceled.

This tool: A check (SerialNumber) is added. Letsencrypt has published a list of critical SerialNumbers, this list is checked. See the part "9. Certificates". If there is a warning, renew that certificate and replace the current certificate.




V

Connect failure - perhaps firewall

Checked:
25.03.2020 22:32:57


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
bloggingbow.com
A
34.89.31.229
Newark/New Jersey/United States (US) - Google LLC
Hostname: 229.31.89.34.bc.googleusercontent.com
yes
1
0

AAAA

yes


www.bloggingbow.com
A
34.89.31.229
Newark/New Jersey/United States (US) - Google LLC
Hostname: 229.31.89.34.bc.googleusercontent.com
yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 33853, Flags 256



Public Key with Algorithm 8, KeyTag 48903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.04.2020, 00:00:00, Signature-Inception: 21.03.2020, 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



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 07.04.2020, 21:00:00, Signature-Inception: 25.03.2020, 20:00:00, KeyTag 33853, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 56311, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 31.03.2020, 18:24:21, Signature-Inception: 16.03.2020, 18:19:21, KeyTag 30909, Signer-Name: com



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 31.03.2020, 18:24:21, Signature-Inception: 16.03.2020, 18: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: bloggingbow.com
bloggingbow.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 domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.Bitmap: NS, DS, RRSIG



0 DNSKEY RR found





Zone: www.bloggingbow.com
www.bloggingbow.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.bloggingbow.com
  ns-cloud-c1.googledomains.com

bloggingbow.com
  ns-cloud-c1.googledomains.com
216.239.32.108
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:32::6c
Ashburn/Virginia/United States (US) - Google LLC


  ns-cloud-c2.googledomains.com
216.239.34.108
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:34::6c
Ashburn/Virginia/United States (US) - Google LLC


  ns-cloud-c3.googledomains.com
216.239.36.108
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:36::6c
Ashburn/Virginia/United States (US) - Google LLC


  ns-cloud-c4.googledomains.com
216.239.38.108
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:38::6c
Ashburn/Virginia/United States (US) - Google LLC

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
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1585171951
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:7


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


Domain:bloggingbow.com
Primary:ns-cloud-c1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:www.bloggingbow.com
Primary:ns-cloud-c1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:1


5. Screenshots (Beta)

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://www.bloggingbow.com/
34.89.31.229
301
http://bloggingbow.com/
0.074
D
Date: Wed, 25 Mar 2020 21:33:33 GMT
Server: Apache/2.4.25 (Debian)
X-Redirect-By: WordPress
Location: http://bloggingbow.com/
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• http://bloggingbow.com/
34.89.31.229
200

0.067
H
Date: Wed, 25 Mar 2020 21:33:33 GMT
Server: Apache/2.4.25 (Debian)
Link: <http://bloggingbow.com/wp-json/>; rel="https://api.w.org/",<http://bloggingbow.com/>; rel=shortlink
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• https://bloggingbow.com/
34.89.31.229
-2

1.080
V
ConnectFailure - Unable to connect to the remote server

• https://www.bloggingbow.com/
34.89.31.229
-2

1.080
V
ConnectFailure - Unable to connect to the remote server

• http://www.bloggingbow.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.89.31.229
301
http://bloggingbow.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
0.074
D
Visible Content:
Date: Wed, 25 Mar 2020 21:33:36 GMT
Server: Apache/2.4.25 (Debian)
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
X-Redirect-By: WordPress
Location: http://bloggingbow.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• http://bloggingbow.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.89.31.229
404

0.090
A
Not Found
Visible Content:
Date: Wed, 25 Mar 2020 21:33:36 GMT
Server: Apache/2.4.25 (Debian)
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Link: <http://bloggingbow.com/wp-json/>; rel="https://api.w.org/"
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

7. Comments

Aname "bloggingbow.com" is domain, 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
Agood - only one version with Http-Status 200
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)
Dhttp://www.bloggingbow.com/ 34.89.31.229
301
http://bloggingbow.com/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.bloggingbow.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.89.31.229
301
http://bloggingbow.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
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://bloggingbow.com/ 34.89.31.229
-2

connect failure - perhaps firewall
Vhttps://www.bloggingbow.com/ 34.89.31.229
-2

connect failure - perhaps firewall
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
AGood: All SOA have the same Serial Number
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-cloud-c1.googledomains.com,ns-cloud-c2.googledomains.com,ns-cloud-c3.googledomains.com,ns-cloud-c4.googledomains.com
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.
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.
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: 70000 milliseconds, 70.000 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)

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

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1512290859
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-22 19:37:52
2020-06-20 19:37:52
bloggingbow.com, www.bloggingbow.com - 2 entries


1512093646
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-22 17:17:16
2020-06-20 17:17:16
bloggingbow.com, www.bloggingbow.com - 2 entries


1512029447
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-22 16:33:07
2020-06-20 16:33:07
bloggingbow.com, www.bloggingbow.com - 2 entries


1511928263
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-22 15:24:56
2020-06-20 15:24:56
bloggingbow.com, www.bloggingbow.com - 2 entries


1511406827
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-22 09:10:48
2020-06-20 09:10:48
bloggingbow.com, www.bloggingbow.com - 2 entries


1498884484
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-16 06:51:09
2020-06-14 06:51:09
*.bloggingbow.com, bloggingbow.com - 2 entries


1367509495
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-16 02:05:08
2020-04-15 02:05:08
*.bloggingbow.com, bloggingbow.com - 2 entries



2. Source crt.sh - old and new certificates, sometimes very slow (Update 2020-01-11: Should now work again - code updated. Old message: currently no newer certificates - read Crt.sh has stopped - Letsencrypt-forum - may work next week again - 2019-12-02 - but I must check the code).

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
7
12

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2613107863
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-22 18:37:52
2020-06-20 17:37:52
bloggingbow.com, www.bloggingbow.com
2 entries


2612769577
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-22 16:17:16
2020-06-20 15:17:16
bloggingbow.com, www.bloggingbow.com
2 entries


2615021366
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-22 15:33:07
2020-06-20 14:33:07
bloggingbow.com, www.bloggingbow.com
2 entries


2612429765
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-22 14:24:56
2020-06-20 13:24:56
bloggingbow.com, www.bloggingbow.com
2 entries


2611454223
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-22 08:10:48
2020-06-20 07:10:48
bloggingbow.com, www.bloggingbow.com
2 entries


2591329086
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-16 05:51:09
2020-06-14 04:51:09
*.bloggingbow.com, bloggingbow.com
2 entries


2344407875
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-16 01:05:08
2020-04-15 00:05:08
*.bloggingbow.com, bloggingbow.com
2 entries


2117050545
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-16 00:49:18
2020-02-14 00:49:18
*.bloggingbow.com, bloggingbow.com
2 entries


1898997035
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-09-17 01:37:55
2019-12-16 02:37:55
*.bloggingbow.com, bloggingbow.com
2 entries


1688353698
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-18 06:55:18
2019-10-16 06:55:18
*.bloggingbow.com, bloggingbow.com
2 entries


1406385026
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-04-21 09:10:49
2019-07-20 09:10:49
*.bloggingbow.com, bloggingbow.com
2 entries


1312387894
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-03-23 02:32:58
2019-06-21 01:32:58
*.bloggingbow.com, bloggingbow.com
2 entries



11. Html-Content - Entries

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


12. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.bloggingbow.com
0

no CAA entry found
1
0
bloggingbow.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


13. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
bloggingbow.com

ok
1
0
www.bloggingbow.com

ok
1
0
_acme-challenge.bloggingbow.com

missing entry or wrong length
1
0
_acme-challenge.www.bloggingbow.com

missing entry or wrong length
1
0
_acme-challenge.bloggingbow.com.bloggingbow.com

perhaps wrong
1
0
_acme-challenge.www.bloggingbow.com.bloggingbow.com

perhaps wrong
1
0
_acme-challenge.www.bloggingbow.com.www.bloggingbow.com

perhaps wrong
1
0


14. Portchecks

Domain or IPPortDescriptionResultAnswer
bloggingbow.com
21
FTP



bloggingbow.com
21
FTP



bloggingbow.com
22
SSH



bloggingbow.com
22
SSH



bloggingbow.com
25
SMTP



bloggingbow.com
25
SMTP



bloggingbow.com
53
DNS



bloggingbow.com
53
DNS



bloggingbow.com
110
POP3



bloggingbow.com
110
POP3



bloggingbow.com
143
IMAP



bloggingbow.com
143
IMAP



bloggingbow.com
465
SMTP (encrypted)



bloggingbow.com
465
SMTP (encrypted)



bloggingbow.com
587
SMTP (encrypted, submission)



bloggingbow.com
587
SMTP (encrypted, submission)



bloggingbow.com
993
IMAP (encrypted)



bloggingbow.com
993
IMAP (encrypted)



bloggingbow.com
995
POP3 (encrypted)



bloggingbow.com
995
POP3 (encrypted)



bloggingbow.com
1433
MS SQL



bloggingbow.com
1433
MS SQL



bloggingbow.com
2082
cPanel (http)



bloggingbow.com
2082
cPanel (http)



bloggingbow.com
2083
cPanel (https)



bloggingbow.com
2083
cPanel (https)



bloggingbow.com
2086
WHM (http)



bloggingbow.com
2086
WHM (http)



bloggingbow.com
2087
WHM (https)



bloggingbow.com
2087
WHM (https)



bloggingbow.com
2089
cPanel Licensing



bloggingbow.com
2089
cPanel Licensing



bloggingbow.com
2095
cPanel Webmail (http)



bloggingbow.com
2095
cPanel Webmail (http)



bloggingbow.com
2096
cPanel Webmail (https)



bloggingbow.com
2096
cPanel Webmail (https)



bloggingbow.com
2222
DirectAdmin (http)



bloggingbow.com
2222
DirectAdmin (http)



bloggingbow.com
2222
DirectAdmin (https)



bloggingbow.com
2222
DirectAdmin (https)



bloggingbow.com
3306
mySql



bloggingbow.com
3306
mySql



bloggingbow.com
5224
Plesk Licensing



bloggingbow.com
5224
Plesk Licensing



bloggingbow.com
5432
PostgreSQL



bloggingbow.com
5432
PostgreSQL



bloggingbow.com
8080
Ookla Speedtest (http)



bloggingbow.com
8080
Ookla Speedtest (http)



bloggingbow.com
8080
Ookla Speedtest (https)



bloggingbow.com
8080
Ookla Speedtest (https)



bloggingbow.com
8083
VestaCP http



bloggingbow.com
8083
VestaCP http



bloggingbow.com
8083
VestaCP https



bloggingbow.com
8083
VestaCP https



bloggingbow.com
8443
Plesk Administration (https)



bloggingbow.com
8443
Plesk Administration (https)



bloggingbow.com
8447
Plesk Installer + Updates



bloggingbow.com
8447
Plesk Installer + Updates



bloggingbow.com
8880
Plesk Administration (http)



bloggingbow.com
8880
Plesk Administration (http)



bloggingbow.com
10000
Webmin (http)



bloggingbow.com
10000
Webmin (http)



bloggingbow.com
10000
Webmin (https)



bloggingbow.com
10000
Webmin (https)



www.bloggingbow.com
21
FTP



www.bloggingbow.com
21
FTP



www.bloggingbow.com
22
SSH



www.bloggingbow.com
22
SSH



www.bloggingbow.com
25
SMTP



www.bloggingbow.com
25
SMTP



www.bloggingbow.com
53
DNS



www.bloggingbow.com
53
DNS



www.bloggingbow.com
110
POP3



www.bloggingbow.com
110
POP3



www.bloggingbow.com
143
IMAP



www.bloggingbow.com
143
IMAP



www.bloggingbow.com
465
SMTP (encrypted)



www.bloggingbow.com
465
SMTP (encrypted)



www.bloggingbow.com
587
SMTP (encrypted, submission)



www.bloggingbow.com
587
SMTP (encrypted, submission)



www.bloggingbow.com
993
IMAP (encrypted)



www.bloggingbow.com
993
IMAP (encrypted)



www.bloggingbow.com
995
POP3 (encrypted)



www.bloggingbow.com
995
POP3 (encrypted)



www.bloggingbow.com
1433
MS SQL



www.bloggingbow.com
1433
MS SQL



www.bloggingbow.com
2082
cPanel (http)



www.bloggingbow.com
2082
cPanel (http)



www.bloggingbow.com
2083
cPanel (https)



www.bloggingbow.com
2083
cPanel (https)



www.bloggingbow.com
2086
WHM (http)



www.bloggingbow.com
2086
WHM (http)



www.bloggingbow.com
2087
WHM (https)



www.bloggingbow.com
2087
WHM (https)



www.bloggingbow.com
2089
cPanel Licensing



www.bloggingbow.com
2089
cPanel Licensing



www.bloggingbow.com
2095
cPanel Webmail (http)



www.bloggingbow.com
2095
cPanel Webmail (http)



www.bloggingbow.com
2096
cPanel Webmail (https)



www.bloggingbow.com
2096
cPanel Webmail (https)



www.bloggingbow.com
2222
DirectAdmin (http)



www.bloggingbow.com
2222
DirectAdmin (http)



www.bloggingbow.com
2222
DirectAdmin (https)



www.bloggingbow.com
2222
DirectAdmin (https)



www.bloggingbow.com
3306
mySql



www.bloggingbow.com
3306
mySql



www.bloggingbow.com
5224
Plesk Licensing



www.bloggingbow.com
5224
Plesk Licensing



www.bloggingbow.com
5432
PostgreSQL



www.bloggingbow.com
5432
PostgreSQL



www.bloggingbow.com
8080
Ookla Speedtest (http)



www.bloggingbow.com
8080
Ookla Speedtest (http)



www.bloggingbow.com
8080
Ookla Speedtest (https)



www.bloggingbow.com
8080
Ookla Speedtest (https)



www.bloggingbow.com
8083
VestaCP http



www.bloggingbow.com
8083
VestaCP http



www.bloggingbow.com
8083
VestaCP https



www.bloggingbow.com
8083
VestaCP https



www.bloggingbow.com
8443
Plesk Administration (https)



www.bloggingbow.com
8443
Plesk Administration (https)



www.bloggingbow.com
8447
Plesk Installer + Updates



www.bloggingbow.com
8447
Plesk Installer + Updates



www.bloggingbow.com
8880
Plesk Administration (http)



www.bloggingbow.com
8880
Plesk Administration (http)



www.bloggingbow.com
10000
Webmin (http)



www.bloggingbow.com
10000
Webmin (http)



www.bloggingbow.com
10000
Webmin (https)



www.bloggingbow.com
10000
Webmin (https)



34.89.31.229
21
FTP



34.89.31.229
21
FTP



34.89.31.229
22
SSH



34.89.31.229
22
SSH



34.89.31.229
25
SMTP



34.89.31.229
25
SMTP



34.89.31.229
53
DNS



34.89.31.229
53
DNS



34.89.31.229
110
POP3



34.89.31.229
110
POP3



34.89.31.229
143
IMAP



34.89.31.229
143
IMAP



34.89.31.229
465
SMTP (encrypted)



34.89.31.229
465
SMTP (encrypted)



34.89.31.229
587
SMTP (encrypted, submission)



34.89.31.229
587
SMTP (encrypted, submission)



34.89.31.229
993
IMAP (encrypted)



34.89.31.229
993
IMAP (encrypted)



34.89.31.229
995
POP3 (encrypted)



34.89.31.229
995
POP3 (encrypted)



34.89.31.229
1433
MS SQL



34.89.31.229
1433
MS SQL



34.89.31.229
2082
cPanel (http)



34.89.31.229
2082
cPanel (http)



34.89.31.229
2083
cPanel (https)



34.89.31.229
2083
cPanel (https)



34.89.31.229
2086
WHM (http)



34.89.31.229
2086
WHM (http)



34.89.31.229
2087
WHM (https)



34.89.31.229
2087
WHM (https)



34.89.31.229
2089
cPanel Licensing



34.89.31.229
2089
cPanel Licensing



34.89.31.229
2095
cPanel Webmail (http)



34.89.31.229
2095
cPanel Webmail (http)



34.89.31.229
2096
cPanel Webmail (https)



34.89.31.229
2096
cPanel Webmail (https)



34.89.31.229
2222
DirectAdmin (http)



34.89.31.229
2222
DirectAdmin (http)



34.89.31.229
2222
DirectAdmin (https)



34.89.31.229
2222
DirectAdmin (https)



34.89.31.229
3306
mySql



34.89.31.229
3306
mySql



34.89.31.229
5224
Plesk Licensing



34.89.31.229
5224
Plesk Licensing



34.89.31.229
5432
PostgreSQL



34.89.31.229
5432
PostgreSQL



34.89.31.229
8080
Ookla Speedtest (http)



34.89.31.229
8080
Ookla Speedtest (http)



34.89.31.229
8080
Ookla Speedtest (https)



34.89.31.229
8080
Ookla Speedtest (https)



34.89.31.229
8083
VestaCP http



34.89.31.229
8083
VestaCP http



34.89.31.229
8083
VestaCP https



34.89.31.229
8083
VestaCP https



34.89.31.229
8443
Plesk Administration (https)



34.89.31.229
8443
Plesk Administration (https)



34.89.31.229
8447
Plesk Installer + Updates



34.89.31.229
8447
Plesk Installer + Updates



34.89.31.229
8880
Plesk Administration (http)



34.89.31.229
8880
Plesk Administration (http)



34.89.31.229
10000
Webmin (http)



34.89.31.229
10000
Webmin (http)



34.89.31.229
10000
Webmin (https)



34.89.31.229
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=1439598e-8d4d-4957-8236-49bbdd8ccf2b


Last Result: https://check-your-website.server-daten.de/?q=bloggingbow.com - 2020-03-25 22:32: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=bloggingbow.com" target="_blank">Check this Site: bloggingbow.com</a>