Appchkr Email Alert Live Demo. Updates after each scan loop.

 -OK-  [x32 buydomains.com] failed to respond starting 2 minutes ago but now has as of 8/12/2022 02:39:01.445031 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x32 buydomains.com]
Cannot connect to www.buydomains.com:443 from nsw3 via tcp after 2 attempt(s) over 4.545991 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
8/12/2022 02:38:05.232205

        ______________________________________________________________________

nsw3_x_500 heartbeat from appchkr on nsw3  
For cfg file /home/Jim/wst/cfg/nsw3_x_500.cfg
Release 1.311, pid 2664
Running 134.606 hours, 7938 loops, since startup on Sat Aug  6 09:24:27 2022 .

Targets Totals:  	0 down  	25 no checking  	475 up

Averages: 	   99.98% up	    0.02% down	for 500 reportable targets 


500 CURRENTLY ACTIVE TARGETS.

8/12/2022 00:00:48.374954

        ______________________________________________________________________

 -OK-  [x397 va.gov] failed to respond starting 2 minutes ago but now has as of 8/11/2022 23:57:39.211328 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x397 va.gov]
Cannot connect to va.gov:443 from nsw3 via tcp after 2 attempt(s) over 4.589727 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
8/11/2022 23:56:42.671203

        ______________________________________________________________________

 -OK-  [x402 ename.com.cn] failed to respond starting 2 minutes ago but now has as of 8/11/2022 21:36:17.868275 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x402 ename.com.cn]
Cannot connect to ename.com.cn:443 from nsw3 via tcp after 2 attempt(s) over 4.554744 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
8/11/2022 21:35:18.859155

        ______________________________________________________________________

 -OK-  [x399 oecd.org] failed to respond starting 2 minutes ago but now has as of 8/11/2022 19:24:58.566956 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x399 oecd.org]
Cannot connect to 78.41.128.129:443 from nsw3 via tcp after 3 attempt(s) over 6.974082 secs. due to:
Connection timed out
[x399 oecd.org] failed to connect to 78.41.128.129:443 by tcp. Try FQDN once.
[x399 oecd.org] failed to connect to oecd.org:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
8/11/2022 19:24:03.389153

        ______________________________________________________________________

 -OK-  [x253 ed.gov] failed to respond starting 7 minutes ago but now has as of 8/11/2022 18:50:13.250394 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x253 ed.gov]
Cannot connect to ed.gov:443 from nsw3 via tcp after 2 attempt(s) over 4.545310 secs. due to:
Connection timed out
Not responding to connection requests for '3' minutes.
8/11/2022 18:46:13.771173

        ______________________________________________________________________

**M** - MEDIUM criticality - [x253 ed.gov]
Cannot connect to ed.gov:443 from nsw3 via tcp after 2 attempt(s) over 4.547422 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
8/11/2022 18:44:12.417135

        ______________________________________________________________________

 -OK-  [x32 buydomains.com] failed to respond starting 2 minutes ago but now has as of 8/11/2022 16:57:08.968885 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x32 buydomains.com]
Cannot connect to www.buydomains.com:443 from nsw3 via tcp after 2 attempt(s) over 4.548080 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
8/11/2022 16:56:12.643146

        ______________________________________________________________________

 -OK-  [x380 nyu.edu] failed to respond starting 6 minutes ago but now has as of 8/11/2022 13:00:26.822647 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x380 nyu.edu]
Cannot connect to nyu.edu:443 from nsw3 via tcp after 2 attempt(s) over 4.556408 secs. due to:
Connection timed out
Not responding to connection requests for '2' minutes.
8/11/2022 12:56:27.601184

        ______________________________________________________________________

 -OK-  [x32 buydomains.com] failed to respond starting 2 minutes ago but now has as of 8/11/2022 06:13:59.494553 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x32 buydomains.com]
Cannot connect to www.buydomains.com:443 from nsw3 via tcp after 2 attempt(s) over 4.605386 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
8/11/2022 06:13:02.470211

        ______________________________________________________________________

*W* Latency is trending up on [x63 wix.com] from cfg file nsw3_x_500 on appchkr on nsw3  :
Avg increased by 0.034007 secs. over the last 10 checks 
to a running avg of 0.055183 secs. as of Thu Aug 11 04:10:55 2022 . 

8/11/2022 04:10:55.764610

        ______________________________________________________________________

 -OK-  [x484 nist.gov] failed to respond starting 3 minutes ago but now has as of 8/11/2022 00:05:12.501363 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x484 nist.gov]
Cannot connect to 129.6.13.49:443 from nsw3 via tcp after 3 attempt(s) over 4.225954 secs. due to:
No route to host
[x484 nist.gov] failed to connect to 129.6.13.49:443 by tcp. Try FQDN once.
[x484 nist.gov] failed to connect to nist.gov:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
8/11/2022 00:03:11.939652

        ______________________________________________________________________

nsw3_x_500 heartbeat from appchkr on nsw3  
For cfg file /home/Jim/wst/cfg/nsw3_x_500.cfg
Release 1.311, pid 2664
Running 110.595 hours, 6522 loops, since startup on Sat Aug  6 09:24:27 2022 .

Targets Totals:  	0 down  	25 no checking  	475 up

Averages: 	   99.97% up	    0.03% down	for 500 reportable targets 


500 CURRENTLY ACTIVE TARGETS.

8/11/2022 00:00:10.483056

        ______________________________________________________________________

 -OK-  [x253 ed.gov] failed to respond starting 11 minutes ago but now has as of 8/10/2022 18:46:37.656777 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x253 ed.gov]
Cannot connect to 165.224.131.199:443 from nsw3 via tcp after 3 attempt(s) over 6.779073 secs. due to:
Connection timed out
[x253 ed.gov] failed to connect to 165.224.131.199:443 by tcp. Try FQDN once.
[x253 ed.gov] failed to connect to ed.gov:443 by tcp using FQDN.
Not responding to connection requests for '9' minutes.
8/10/2022 18:44:41.011149

        ______________________________________________________________________

**M** - MEDIUM criticality - [x253 ed.gov]
Cannot connect to 165.224.131.199:443 from nsw3 via tcp after 3 attempt(s) over 6.773858 secs. due to:
Connection timed out
[x253 ed.gov] failed to connect to 165.224.131.199:443 by tcp. Try FQDN once.
[x253 ed.gov] failed to connect to ed.gov:443 by tcp using FQDN.
Not responding to connection requests for '4' minutes.
8/10/2022 18:39:34.745171

        ______________________________________________________________________

**M** - MEDIUM criticality - [x253 ed.gov]
Cannot connect to 165.224.131.199:443 from nsw3 via tcp after 3 attempt(s) over 6.788345 secs. due to:
Connection timed out
[x253 ed.gov] failed to connect to 165.224.131.199:443 by tcp. Try FQDN once.
[x253 ed.gov] failed to connect to ed.gov:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
8/10/2022 18:36:32.401274

        ______________________________________________________________________

 -OK-  [x333 1688.com] failed to respond starting 18 minutes ago but now has as of 8/10/2022 14:31:18.890996 .

        ______________________________________________________________________

 -OK-  [x280 youku.com] failed to respond starting 3 minutes ago but now has as of 8/10/2022 14:25:10.471834 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x280 youku.com]
Cannot connect to youku.com:443 from nsw3 via tcp after 2 attempt(s) over 3.025923 secs. due to:
Connection refused
Not responding to connection requests for '1' minutes.
8/10/2022 14:23:09.518449

        ______________________________________________________________________

**M** - MEDIUM criticality - [x333 1688.com]
Cannot connect to 1688.com:443 from nsw3 via tcp after 2 attempt(s) over 2.148381 secs. due to:
Connection refused
Not responding to connection requests for '9' minutes.
8/10/2022 14:22:10.621088

        ______________________________________________________________________

**M** - MEDIUM criticality - [x333 1688.com]
Cannot connect to 1688.com:443 from nsw3 via tcp after 2 attempt(s) over 1.438494 secs. due to:
Connection refused
Not responding to connection requests for '3' minutes.
8/10/2022 14:16:05.564317

        ______________________________________________________________________

**M** - MEDIUM criticality - [x333 1688.com]
Cannot connect to 1688.com:443 from nsw3 via tcp after 2 attempt(s) over 1.142601 secs. due to:
Connection refused
Not responding to connection requests for '1' minutes.
8/10/2022 14:14:01.846469

        ______________________________________________________________________

 -OK-  [x32 buydomains.com] failed to respond starting 2 minutes ago but now has as of 8/10/2022 03:45:06.379119 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x32 buydomains.com]
Cannot connect to www.buydomains.com:443 from nsw3 via tcp after 2 attempt(s) over 4.541945 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
8/10/2022 03:44:10.337204

        ______________________________________________________________________

 -OK-  [x32 buydomains.com] failed to respond starting 2 minutes ago but now has as of 8/10/2022 00:29:43.767200 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x32 buydomains.com]
Cannot connect to www.buydomains.com:443 from nsw3 via tcp after 2 attempt(s) over 4.551774 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
8/10/2022 00:28:47.055190

        ______________________________________________________________________

nsw3_x_500 heartbeat from appchkr on nsw3  
For cfg file /home/Jim/wst/cfg/nsw3_x_500.cfg
Release 1.311, pid 2664
Running 86.604 hours, 5107 loops, since startup on Sat Aug  6 09:24:27 2022 .

Targets Totals:  	0 down  	25 no checking  	475 up

Averages: 	   99.97% up	    0.03% down	for 500 reportable targets 


500 CURRENTLY ACTIVE TARGETS.

8/10/2022 00:00:42.405111

        ______________________________________________________________________

*W* Latency is trending up on [x494 aarp.org] from cfg file nsw3_x_500 on appchkr on nsw3  :
Avg increased by 0.051059 secs. over the last 10 checks 
to a running avg of 0.082129 secs. as of Tue Aug  9 22:38:16 2022 . 

8/9/2022 22:38:16.750903

        ______________________________________________________________________

 -OK-  [x402 ename.com.cn] failed to respond starting 3 minutes ago but now has as of 8/9/2022 15:57:29.059519 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x402 ename.com.cn]
Cannot connect to ename.com.cn:443 from nsw3 via tcp after 2 attempt(s) over 4.832659 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
8/9/2022 15:55:39.698165

        ______________________________________________________________________

 -OK-  [x46 addthis.com] failed to respond starting 2 minutes ago but now has as of 8/9/2022 13:36:36.990929 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x46 addthis.com]
Cannot connect to 23.38.84.123:443 from nsw3 via tcp after 3 attempt(s) over 6.778342 secs. due to:
Connection timed out
[x46 addthis.com] failed to connect to 23.38.84.123:443 by tcp. Try FQDN once.
[x46 addthis.com] failed to connect to addthis.com:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
8/9/2022 13:35:42.689147

        ______________________________________________________________________

 -OK-  [x224 nps.gov] failed to respond starting 562 minutes ago but now has as of 8/9/2022 11:35:46.436854 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x224 nps.gov]
Cannot connect to 52.6.8.53:443 from nsw3 via tcp after 3 attempt(s) over 6.781840 secs. due to:
Connection timed out
[x224 nps.gov] failed to connect to 52.6.8.53:443 by tcp. Try FQDN once.
[x224 nps.gov] failed to connect to nps.gov:443 by tcp using FQDN.
Not responding to connection requests for '341' minutes.
8/9/2022 07:55:07.992175

        ______________________________________________________________________

**M** - MEDIUM criticality - [x224 nps.gov]
Cannot connect to 52.6.8.53:443 from nsw3 via tcp after 3 attempt(s) over 6.788236 secs. due to:
Connection timed out
[x224 nps.gov] failed to connect to 52.6.8.53:443 by tcp. Try FQDN once.
[x224 nps.gov] failed to connect to nps.gov:443 by tcp using FQDN.
Not responding to connection requests for '180' minutes.
8/9/2022 05:13:26.497187

        ______________________________________________________________________

**M** - MEDIUM criticality - [x224 nps.gov]
Cannot connect to 52.6.8.53:443 from nsw3 via tcp after 3 attempt(s) over 6.782094 secs. due to:
Connection timed out
[x224 nps.gov] failed to connect to 52.6.8.53:443 by tcp. Try FQDN once.
[x224 nps.gov] failed to connect to nps.gov:443 by tcp using FQDN.
Not responding to connection requests for '89' minutes.
8/9/2022 03:42:54.215159

        ______________________________________________________________________

**M** - MEDIUM criticality - [x224 nps.gov]
Cannot connect to 52.6.8.53:443 from nsw3 via tcp after 3 attempt(s) over 6.783982 secs. due to:
Connection timed out
[x224 nps.gov] failed to connect to 52.6.8.53:443 by tcp. Try FQDN once.
[x224 nps.gov] failed to connect to nps.gov:443 by tcp using FQDN.
Not responding to connection requests for '43' minutes.
8/9/2022 02:57:09.546181

        ______________________________________________________________________

**M** - MEDIUM criticality - [x224 nps.gov]
Cannot connect to 52.6.8.53:443 from nsw3 via tcp after 3 attempt(s) over 6.780791 secs. due to:
Connection timed out
[x224 nps.gov] failed to connect to 52.6.8.53:443 by tcp. Try FQDN once.
[x224 nps.gov] failed to connect to nps.gov:443 by tcp using FQDN.
Not responding to connection requests for '20' minutes.
8/9/2022 02:33:43.024161

        ______________________________________________________________________

**M** - MEDIUM criticality - [x224 nps.gov]
Cannot connect to 52.6.8.53:443 from nsw3 via tcp after 3 attempt(s) over 6.778785 secs. due to:
Connection timed out
[x224 nps.gov] failed to connect to 52.6.8.53:443 by tcp. Try FQDN once.
[x224 nps.gov] failed to connect to nps.gov:443 by tcp using FQDN.
Not responding to connection requests for '7' minutes.
8/9/2022 02:20:30.449162

        ______________________________________________________________________

**M** - MEDIUM criticality - [x224 nps.gov]
Cannot connect to 52.6.8.53:443 from nsw3 via tcp after 3 attempt(s) over 6.779811 secs. due to:
Connection timed out
[x224 nps.gov] failed to connect to 52.6.8.53:443 by tcp. Try FQDN once.
[x224 nps.gov] failed to connect to nps.gov:443 by tcp using FQDN.
Not responding to connection requests for '3' minutes.
8/9/2022 02:16:25.868193

        ______________________________________________________________________

**M** - MEDIUM criticality - [x224 nps.gov]
Cannot connect to 52.6.8.53:443 from nsw3 via tcp after 3 attempt(s) over 6.783557 secs. due to:
Connection timed out
[x224 nps.gov] failed to connect to 52.6.8.53:443 by tcp. Try FQDN once.
[x224 nps.gov] failed to connect to nps.gov:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
8/9/2022 02:14:23.316265

        ______________________________________________________________________

 -OK-  [x224 nps.gov] failed to respond starting 38 minutes ago but now has as of 8/9/2022 01:03:06.011769 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x224 nps.gov]
Cannot connect to 52.6.8.53:443 from nsw3 via tcp after 3 attempt(s) over 6.790406 secs. due to:
Connection timed out
[x224 nps.gov] failed to connect to 52.6.8.53:443 by tcp. Try FQDN once.
[x224 nps.gov] failed to connect to nps.gov:443 by tcp using FQDN.
Not responding to connection requests for '20' minutes.
8/9/2022 00:44:54.678170

        ______________________________________________________________________

**M** - MEDIUM criticality - [x224 nps.gov]
Cannot connect to 52.6.8.53:443 from nsw3 via tcp after 3 attempt(s) over 6.780483 secs. due to:
Connection timed out
[x224 nps.gov] failed to connect to 52.6.8.53:443 by tcp. Try FQDN once.
[x224 nps.gov] failed to connect to nps.gov:443 by tcp using FQDN.
Not responding to connection requests for '9' minutes.
8/9/2022 00:33:42.186137

        ______________________________________________________________________

**M** - MEDIUM criticality - [x224 nps.gov]
Cannot connect to 52.6.8.53:443 from nsw3 via tcp after 3 attempt(s) over 6.780980 secs. due to:
Connection timed out
[x224 nps.gov] failed to connect to 52.6.8.53:443 by tcp. Try FQDN once.
[x224 nps.gov] failed to connect to nps.gov:443 by tcp using FQDN.
Not responding to connection requests for '4' minutes.
8/9/2022 00:28:38.364159

        ______________________________________________________________________

**M** - MEDIUM criticality - [x224 nps.gov]
Cannot connect to 52.6.8.53:443 from nsw3 via tcp after 3 attempt(s) over 6.781955 secs. due to:
Connection timed out
[x224 nps.gov] failed to connect to 52.6.8.53:443 by tcp. Try FQDN once.
[x224 nps.gov] failed to connect to nps.gov:443 by tcp using FQDN.
Not responding to connection requests for '2' minutes.
8/9/2022 00:26:35.287174

        ______________________________________________________________________

nsw3_x_500 heartbeat from appchkr on nsw3  
For cfg file /home/Jim/wst/cfg/nsw3_x_500.cfg
Release 1.311, pid 2664
Running 62.598 hours, 3691 loops, since startup on Sat Aug  6 09:24:27 2022 .

Targets Totals:  	0 down  	25 no checking  	475 up

Averages: 	   99.99% up	    0.01% down	for 500 reportable targets 


500 CURRENTLY ACTIVE TARGETS.

8/9/2022 00:00:19.831849

        ______________________________________________________________________

*W* Latency is trending up on [x63 wix.com] from cfg file nsw3_x_500 on appchkr on nsw3  :
Avg increased by 0.033462 secs. over the last 10 checks 
to a running avg of 0.054745 secs. as of Mon Aug  8 05:20:48 2022 . 

8/8/2022 05:20:49.004966

        ______________________________________________________________________

 -OK-  [x372 cam.ac.uk] failed to respond starting 5 minutes ago but now has as of 8/8/2022 02:13:55.023084 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x372 cam.ac.uk]
Cannot connect to 128.232.132.8:443 from nsw3 via tcp after 3 attempt(s) over 6.778005 secs. due to:
Connection timed out
[x372 cam.ac.uk] failed to connect to 128.232.132.8:443 by tcp. Try FQDN once.
[x372 cam.ac.uk] failed to connect to cam.ac.uk:443 by tcp using FQDN.
Not responding to connection requests for '3' minutes.
8/8/2022 02:12:01.447228

        ______________________________________________________________________

**M** - MEDIUM criticality - [x372 cam.ac.uk]
Cannot connect to 128.232.132.8:443 from nsw3 via tcp after 3 attempt(s) over 6.853497 secs. due to:
Connection timed out
[x372 cam.ac.uk] failed to connect to 128.232.132.8:443 by tcp. Try FQDN once.
[x372 cam.ac.uk] failed to connect to cam.ac.uk:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
8/8/2022 02:09:58.201161

        ______________________________________________________________________

 -OK-  [x372 cam.ac.uk] failed to respond starting 5 minutes ago but now has as of 8/8/2022 02:00:40.035548 .

        ______________________________________________________________________

**M** - MEDIUM criticality - [x372 cam.ac.uk]
Cannot connect to 128.232.132.8:443 from nsw3 via tcp after 3 attempt(s) over 6.776694 secs. due to:
Connection timed out
[x372 cam.ac.uk] failed to connect to 128.232.132.8:443 by tcp. Try FQDN once.
[x372 cam.ac.uk] failed to connect to cam.ac.uk:443 by tcp using FQDN.
Not responding to connection requests for '4' minutes.
8/8/2022 01:59:45.052165

        ______________________________________________________________________

**M** - MEDIUM criticality - [x372 cam.ac.uk]
Cannot connect to 128.232.132.8:443 from nsw3 via tcp after 3 attempt(s) over 6.775905 secs. due to:
Connection timed out
[x372 cam.ac.uk] failed to connect to 128.232.132.8:443 by tcp. Try FQDN once.
[x372 cam.ac.uk] failed to connect to cam.ac.uk:443 by tcp using FQDN.
Not responding to connection requests for '2' minutes.
8/8/2022 01:57:44.003198
... truncated to the first '500' lines.