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

nsw3_x_500 heartbeat from appchkr on nsw3  
For cfg file /home/Jim/wst/cfg/nsw3_x_500.cfg
Release 1.07, pid 12884
Running 777.038 hours, 45818 loops, since startup on Tue Jan 21 14:58:22 2020 .

Targets Totals:  	1 down  	19 no checking  	480 up

Averages: 	   99.76% up	    0.24% down	for 500 reportable targets 


500 CURRENTLY ACTIVE TARGETS.

2/23/2020 00:00:38.939735

 -OK-  [x218 epa.gov] failed to respond starting 9 minutes ago but now has as of 2/22/2020 15:38:46.271798 .

**M** - MEDIUM criticality - [x218 epa.gov]
Cannot connect to epa.gov:443 from nsw3 via tcp after 2 attempt(s) over 4.557119 secs. due to:
Connection timed out
Not responding to connection requests for '8' minutes.
2/22/2020 15:37:50.014848

**M** - MEDIUM criticality - [x218 epa.gov]
Cannot connect to epa.gov:443 from nsw3 via tcp after 2 attempt(s) over 4.554729 secs. due to:
Connection timed out
Not responding to connection requests for '4' minutes.
2/22/2020 15:33:45.002471

**M** - MEDIUM criticality - [x218 epa.gov]
Cannot connect to epa.gov:443 from nsw3 via tcp after 2 attempt(s) over 4.548215 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
2/22/2020 15:30:43.243982

 -OK-  [x218 epa.gov] failed to respond starting 11 minutes ago but now has as of 2/22/2020 15:28:39.157144 .

**M** - MEDIUM criticality - [x218 epa.gov]
Cannot connect to epa.gov:443 from nsw3 via tcp after 2 attempt(s) over 4.556809 secs. due to:
Connection timed out
Not responding to connection requests for '7' minutes.
2/22/2020 15:24:36.513943

**M** - MEDIUM criticality - [x218 epa.gov]
Cannot connect to epa.gov:443 from nsw3 via tcp after 2 attempt(s) over 4.556112 secs. due to:
Connection timed out
Not responding to connection requests for '3' minutes.
2/22/2020 15:20:31.019306

**M** - MEDIUM criticality - [x218 epa.gov]
Cannot connect to epa.gov:443 from nsw3 via tcp after 2 attempt(s) over 4.571901 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
2/22/2020 15:18:28.026462

 -OK-  [x218 epa.gov] failed to respond starting 4 minutes ago but now has as of 2/22/2020 15:08:14.245727 .

**M** - MEDIUM criticality - [x218 epa.gov]
Cannot connect to epa.gov:443 from nsw3 via tcp after 2 attempt(s) over 4.571226 secs. due to:
Connection timed out
Not responding to connection requests for '2' minutes.
2/22/2020 15:06:14.752505

 -OK-  [x425 ietf.org] failed to respond starting 34 minutes ago but now has as of 2/22/2020 12:39:00.241439 .

**M** - MEDIUM criticality - [x425 ietf.org]
Cannot connect to 4.31.198.44:443 from nsw3 via tcp after 3 attempt(s) over 0.998789 secs. due to:
Connection refused
[x425 ietf.org] failed to connect to 4.31.198.44:443 by tcp. Try FQDN once.
[x425 ietf.org] failed to connect to ietf.org:443 by tcp using FQDN.
Not responding to connection requests for '24' minutes.
2/22/2020 12:28:54.047621

**M** - MEDIUM criticality - [x425 ietf.org]
Cannot connect to 4.31.198.44:443 from nsw3 via tcp after 3 attempt(s) over 0.998456 secs. due to:
Connection refused
[x425 ietf.org] failed to connect to 4.31.198.44:443 by tcp. Try FQDN once.
[x425 ietf.org] failed to connect to ietf.org:443 by tcp using FQDN.
Not responding to connection requests for '12' minutes.
2/22/2020 12:16:38.834728

**M** - MEDIUM criticality - [x425 ietf.org]
Cannot connect to 4.31.198.44:443 from nsw3 via tcp after 3 attempt(s) over 1.068105 secs. due to:
Connection refused
[x425 ietf.org] failed to connect to 4.31.198.44:443 by tcp. Try FQDN once.
[x425 ietf.org] failed to connect to ietf.org:443 by tcp using FQDN.
Not responding to connection requests for '5' minutes.
2/22/2020 12:09:31.275317

**M** - MEDIUM criticality - [x425 ietf.org]
Cannot connect to 4.31.198.44:443 from nsw3 via tcp after 3 attempt(s) over 1.078313 secs. due to:
Connection refused
[x425 ietf.org] failed to connect to 4.31.198.44:443 by tcp. Try FQDN once.
[x425 ietf.org] failed to connect to ietf.org:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
2/22/2020 12:05:33.303628

 -OK-  [x387 bls.gov] failed to respond starting 203 minutes ago but now has as of 2/22/2020 11:58:14.753991 .

**M** - MEDIUM criticality - [x387 bls.gov]
Cannot connect to bls.gov:443 from nsw3 via tcp after 2 attempt(s) over 2.666438 secs. due to:
Connection timed out
Not responding to connection requests for '104' minutes.
2/22/2020 10:19:35.321806

**M** - MEDIUM criticality - [x387 bls.gov]
Cannot connect to bls.gov:443 from nsw3 via tcp after 2 attempt(s) over 3.976241 secs. due to:
Connection timed out
Not responding to connection requests for '52' minutes.
2/22/2020 09:27:43.425405

**M** - MEDIUM criticality - [x387 bls.gov]
Cannot connect to bls.gov:443 from nsw3 via tcp after 2 attempt(s) over 2.627951 secs. due to:
Connection timed out
Not responding to connection requests for '26' minutes.
2/22/2020 09:01:13.774505

**M** - MEDIUM criticality - [x387 bls.gov]
Cannot connect to bls.gov:443 from nsw3 via tcp after 2 attempt(s) over 4.286894 secs. due to:
No route to host
Not responding to connection requests for '12' minutes.
2/22/2020 08:47:02.854682

**M** - MEDIUM criticality - [x387 bls.gov]
Cannot connect to bls.gov:443 from nsw3 via tcp after 2 attempt(s) over 3.288880 secs. due to:
No route to host
Not responding to connection requests for '5' minutes.
2/22/2020 08:39:52.664646

**M** - MEDIUM criticality - [x387 bls.gov]
Cannot connect to bls.gov:443 from nsw3 via tcp after 2 attempt(s) over 3.157703 secs. due to:
Connection timed out
Not responding to connection requests for '2' minutes.
2/22/2020 08:36:48.478361

nsw3_x_500 heartbeat from appchkr on nsw3  
For cfg file /home/Jim/wst/cfg/nsw3_x_500.cfg
Release 1.07, pid 12884
Running 753.029 hours, 44402 loops, since startup on Tue Jan 21 14:58:22 2020 .

Targets Totals:  	1 down  	19 no checking  	480 up

Averages: 	   99.76% up	    0.24% down	for 500 reportable targets 


500 CURRENTLY ACTIVE TARGETS.

2/22/2020 00:00:06.391901

 -OK-  [x277 hostnet.nl] failed to respond starting 7 minutes ago but now has as of 2/21/2020 20:07:47.527745 .

**M** - MEDIUM criticality - [x277 hostnet.nl]
Cannot connect to hostnet.nl:443 from nsw3 via tcp after 2 attempt(s) over 4.541968 secs. due to:
Connection timed out
Not responding to connection requests for '4' minutes.
2/21/2020 20:04:48.710375

**M** - MEDIUM criticality - [x277 hostnet.nl]
Cannot connect to hostnet.nl:443 from nsw3 via tcp after 2 attempt(s) over 4.549969 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
2/21/2020 20:02:45.533982

 -OK-  [x243 themegrill.com] failed to respond starting 3 minutes ago but now has as of 2/21/2020 14:38:06.394667 .

**M** - MEDIUM criticality - [x243 themegrill.com]
Cannot connect to themegrill.com:443 from nsw3 via tcp after 2 attempt(s) over 4.549649 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
2/21/2020 14:36:07.755410

 -OK-  [x324 sagepub.com] failed to respond starting 2 minutes ago but now has as of 2/21/2020 14:08:41.891287 .

**M** - MEDIUM criticality - [x324 sagepub.com]
Cannot connect to sagepub.com:443 from nsw3 via tcp after 2 attempt(s) over 4.548110 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
2/21/2020 14:07:43.791822

 -OK-  [x454 artisteer.com] failed to respond starting 5 minutes ago but now has as of 2/21/2020 02:17:40.694011 .

**M** - MEDIUM criticality - [x454 artisteer.com]
Cannot connect to artisteer.com:443 from nsw3 via tcp after 2 attempt(s) over 3.989832 secs. due to:
Connection timed out
Not responding to connection requests for '2' minutes.
2/21/2020 02:14:41.927468

 -OK-  [x300 upenn.edu] failed to respond starting 3 minutes ago but now has as of 2/21/2020 01:24:49.083710 .

**M** - MEDIUM criticality - [x300 upenn.edu]
Cannot connect to 130.91.210.133:443 from nsw3 via tcp after 3 attempt(s) over 6.775475 secs. due to:
Connection timed out
[x300 upenn.edu] failed to connect to 130.91.210.133:443 by tcp. Try FQDN once.
[x300 upenn.edu] failed to connect to upenn.edu:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
2/21/2020 01:23:43.316855

 -OK-  [x324 sagepub.com] failed to respond starting 3 minutes ago but now has as of 2/21/2020 01:17:38.436671 .

**M** - MEDIUM criticality - [x324 sagepub.com]
Cannot connect to sagepub.com:443 from nsw3 via tcp after 2 attempt(s) over 4.545257 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
2/21/2020 01:15:42.007583

nsw3_x_500 heartbeat from appchkr on nsw3  
For cfg file /home/Jim/wst/cfg/nsw3_x_500.cfg
Release 1.07, pid 12884
Running 729.036 hours, 42987 loops, since startup on Tue Jan 21 14:58:22 2020 .

Targets Totals:  	1 down  	19 no checking  	480 up

Averages: 	   99.76% up	    0.24% down	for 500 reportable targets 


500 CURRENTLY ACTIVE TARGETS.

2/21/2020 00:00:31.201288

*W* Latency is trending up on [x2 twitter.com] from cfg file nsw3_x_500 on appchkr on nsw3  :
Avg increased by 0.026423 secs. over the last 10 checks 
to a running avg of 0.063315 secs. as of Thu Feb 20 23:27:19 2020 . 

2/20/2020 23:27:19.994801

 -OK-  [x454 artisteer.com] failed to respond starting 2 minutes ago but now has as of 2/20/2020 18:30:43.690181 .

**M** - MEDIUM criticality - [x454 artisteer.com]
Cannot connect to artisteer.com:443 from nsw3 via tcp after 2 attempt(s) over 4.549216 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
2/20/2020 18:29:44.172832

 -OK-  [x324 sagepub.com] failed to respond starting 2 minutes ago but now has as of 2/20/2020 17:28:32.586705 .

**M** - MEDIUM criticality - [x324 sagepub.com]
Cannot connect to sagepub.com:443 from nsw3 via tcp after 2 attempt(s) over 4.546633 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
2/20/2020 17:27:36.341837

nsw3_x_500 heartbeat from appchkr on nsw3  
For cfg file /home/Jim/wst/cfg/nsw3_x_500.cfg
Release 1.07, pid 12884
Running 705.039 hours, 41572 loops, since startup on Tue Jan 21 14:58:22 2020 .

Targets Totals:  	1 down  	19 no checking  	480 up

Averages: 	   99.76% up	    0.24% down	for 500 reportable targets 


500 CURRENTLY ACTIVE TARGETS.

2/20/2020 00:00:43.421546

 -OK-  [x218 epa.gov] failed to respond starting 3 minutes ago but now has as of 2/19/2020 22:51:11.437679 .

**M** - MEDIUM criticality - [x218 epa.gov]
Cannot connect to epa.gov:443 from nsw3 via tcp after 2 attempt(s) over 15.55694 secs. due to:
Connection timed out
Not responding to connection requests for '1' minutes.
2/19/2020 22:49:25.691022

 -OK-  [x218 epa.gov] failed to respond starting 3 minutes ago but now has as of 2/19/2020 22:45:01.748386 .

**M** - MEDIUM criticality - [x218 epa.gov]
Cannot connect to 134.67.21.34:443 from nsw3 via tcp after 3 attempt(s) over 15.68017 secs. due to:
Connection timed out
[x218 epa.gov] failed to connect to 134.67.21.34:443 by tcp. Try FQDN once.
[x218 epa.gov] failed to connect to epa.gov:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
2/19/2020 22:43:05.960393

 -OK-  [x220 enable-javascript.com] failed to respond starting 2 minutes ago but now has as of 2/19/2020 18:19:16.014963 .

**M** - MEDIUM criticality - [x220 enable-javascript.com]
Cannot connect to 185.58.74.239:443 from nsw3 via tcp after 3 attempt(s) over 6.874428 secs. due to:
Connection timed out
[x220 enable-javascript.com] failed to connect to 185.58.74.239:443 by tcp. Try FQDN once.
[x220 enable-javascript.com] failed to connect to enable-javascript.com:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
2/19/2020 18:18:21.872319

*W* Latency is trending up on [x141 gnu.org] from cfg file nsw3_x_500 on appchkr on nsw3  :
Avg increased by 0.018189 secs. over the last 10 checks 
to a running avg of 0.038539 secs. as of Wed Feb 19 17:01:55 2020 . 

2/19/2020 17:01:55.123709

**M** - MEDIUM criticality - [x197 cloudfront.net]
Cannot connect to cloudfront.net:443 from nsw3 via tcp after 1 attempt(s) over 0.286342 secs. due to:
Invalid argument
Not responding to connection requests for '26769' minutes.
2/19/2020 14:11:02.721720

nsw3_x_500 heartbeat from appchkr on nsw3  
For cfg file /home/Jim/wst/cfg/nsw3_x_500.cfg
Release 1.07, pid 12884
Running 681.043 hours, 40157 loops, since startup on Tue Jan 21 14:58:22 2020 .

Targets Totals:  	1 down  	19 no checking  	480 up

Averages: 	   99.75% up	    0.25% down	for 500 reportable targets 


500 CURRENTLY ACTIVE TARGETS.

2/19/2020 00:00:55.959212

 -OK-  [x82 parallels.com] failed to respond starting 2 minutes ago but now has as of 2/18/2020 22:43:05.831023 .

**M** - MEDIUM criticality - [x82 parallels.com]
Cannot connect to 195.214.234.136:443 from nsw3 via tcp after 3 attempt(s) over 6.780537 secs. due to:
Connection timed out
[x82 parallels.com] failed to connect to 195.214.234.136:443 by tcp. Try FQDN once.
[x82 parallels.com] failed to connect to parallels.com:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
2/18/2020 22:42:11.193513

 -OK-  [x220 enable-javascript.com] failed to respond starting 7 minutes ago but now has as of 2/18/2020 17:49:15.587121 .

**M** - MEDIUM criticality - [x220 enable-javascript.com]
Cannot connect to 185.58.74.239:443 from nsw3 via tcp after 3 attempt(s) over 1.120872 secs. due to:
Connection refused
[x220 enable-javascript.com] failed to connect to 185.58.74.239:443 by tcp. Try FQDN once.
[x220 enable-javascript.com] failed to connect to enable-javascript.com:443 by tcp using FQDN.
Not responding to connection requests for '3' minutes.
2/18/2020 17:45:14.163879

**M** - MEDIUM criticality - [x220 enable-javascript.com]
Cannot connect to 185.58.74.239:443 from nsw3 via tcp after 3 attempt(s) over 1.117453 secs. due to:
Connection refused
[x220 enable-javascript.com] failed to connect to 185.58.74.239:443 by tcp. Try FQDN once.
[x220 enable-javascript.com] failed to connect to enable-javascript.com:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
2/18/2020 17:43:11.657550

 -OK-  [x452 domeneshop.no] failed to respond starting 3 minutes ago but now has as of 2/18/2020 15:34:17.059808 .

 -OK-  [x440 domainnameshop.com] failed to respond starting 3 minutes ago but now has as of 2/18/2020 15:33:15.954857 .

**M** - MEDIUM criticality - [x452 domeneshop.no]
Cannot connect to 194.63.251.25:443 from nsw3 via tcp after 3 attempt(s) over 6.785928 secs. due to:
Connection timed out
[x452 domeneshop.no] failed to connect to 194.63.251.25:443 by tcp. Try FQDN once.
[x452 domeneshop.no] failed to connect to domeneshop.no:443 by tcp using FQDN.
Not responding to connection requests for '2' minutes.
2/18/2020 15:32:28.323655

**M** - MEDIUM criticality - [x440 domainnameshop.com]
Cannot connect to 194.63.251.21:443 from nsw3 via tcp after 3 attempt(s) over 6.888555 secs. due to:
Connection timed out
[x440 domainnameshop.com] failed to connect to 194.63.251.21:443 by tcp. Try FQDN once.
[x440 domainnameshop.com] failed to connect to domainnameshop.com:443 by tcp using FQDN.
Not responding to connection requests for '2' minutes.
2/18/2020 15:32:20.748993

 -OK-  [x189 networksolutions.com] failed to respond starting 7 minutes ago but now has as of 2/18/2020 05:07:14.422026 .

**M** - MEDIUM criticality - [x189 networksolutions.com]
Cannot connect to networksolutions.com:443 from nsw3 via tcp after 2 attempt(s) over 12.66547 secs. due to:
Invalid argument
Not responding to connection requests for '4' minutes.
2/18/2020 05:04:22.566224

**M** - MEDIUM criticality - [x189 networksolutions.com]
Cannot connect to networksolutions.com:443 from nsw3 via tcp after 2 attempt(s) over 12.68732 secs. due to:
Invalid argument
Not responding to connection requests for '1' minutes.
2/18/2020 05:01:23.129733

 -OK-  [x189 networksolutions.com] failed to respond starting 3 minutes ago but now has as of 2/18/2020 04:10:11.781221 .

**M** - MEDIUM criticality - [x189 networksolutions.com]
Cannot connect to networksolutions.com:443 from nsw3 via tcp after 2 attempt(s) over 12.67560 secs. due to:
Invalid argument
Not responding to connection requests for '1' minutes.
2/18/2020 04:08:15.037631

 -OK-  [x342 mijndomein.nl] failed to respond starting 3 minutes ago but now has as of 2/18/2020 00:08:53.430610 .

**M** - MEDIUM criticality - [x342 mijndomein.nl]
Cannot connect to 81.4.97.160:443 from nsw3 via tcp after 3 attempt(s) over 5.394645 secs. due to:
No route to host
[x342 mijndomein.nl] failed to connect to 81.4.97.160:443 by tcp. Try FQDN once.
[x342 mijndomein.nl] failed to connect to mijndomein.nl:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
2/18/2020 00:06:59.511356

nsw3_x_500 heartbeat from appchkr on nsw3  
For cfg file /home/Jim/wst/cfg/nsw3_x_500.cfg
Release 1.07, pid 12884
Running 657.042 hours, 38742 loops, since startup on Tue Jan 21 14:58:22 2020 .

Targets Totals:  	1 down  	19 no checking  	480 up

Averages: 	   99.75% up	    0.25% down	for 500 reportable targets 


500 CURRENTLY ACTIVE TARGETS.

2/18/2020 00:00:54.985220

 -OK-  [x425 ietf.org] failed to respond starting 7 minutes ago but now has as of 2/17/2020 21:17:03.084790 .

**M** - MEDIUM criticality - [x425 ietf.org]
Cannot connect to 4.31.198.44:443 from nsw3 via tcp after 3 attempt(s) over 6.775241 secs. due to:
Connection timed out
[x425 ietf.org] failed to connect to 4.31.198.44:443 by tcp. Try FQDN once.
[x425 ietf.org] failed to connect to ietf.org:443 by tcp using FQDN.
Not responding to connection requests for '5' minutes.
2/17/2020 21:15:06.116693

**M** - MEDIUM criticality - [x425 ietf.org]
Cannot connect to 4.31.198.44:443 from nsw3 via tcp after 3 attempt(s) over 6.780341 secs. due to:
Connection timed out
[x425 ietf.org] failed to connect to 4.31.198.44:443 by tcp. Try FQDN once.
[x425 ietf.org] failed to connect to ietf.org:443 by tcp using FQDN.
Not responding to connection requests for '1' minutes.
2/17/2020 21:11:05.367270

*W* Latency is trending up on [x448 windowsphone.com] from cfg file nsw3_x_500 on appchkr on nsw3  :
Avg increased by 0.038441 secs. over the last 10 checks 
to a running avg of 0.058420 secs. as of Mon Feb 17 14:44:19 2020 . 

2/17/2020 14:44:19.573059

*W* Latency is trending up on [x176 plesk.com] from cfg file nsw3_x_500 on appchkr on nsw3  :
Avg increased by 0.047021 secs. over the last 10 checks 
to a running avg of 0.077345 secs. as of Mon Feb 17 14:40:57 2020 . 

2/17/2020 14:40:58.094419

*W* Latency is trending up on [x114 tripadvisor.com] from cfg file nsw3_x_500 on appchkr on nsw3  :
Avg increased by 0.097569 secs. over the last 10 checks 
to a running avg of 0.176446 secs. as of Mon Feb 17 14:40:54 2020 . 

2/17/2020 14:40:54.904012

 -CFG- appchkr on nsw3 changed by /home/Jim/wst/cfg/nsw3_x_500.cfg 
Configuration differences are:


[x100 hatena.ne.jp] Old vs. New: _hostbegin from hatena.ne.jp to 54.64.59.84
[x100 hatena.ne.jp] Old vs. New: new_IP from 0 to _none_

[x101 bloomberg.com] Old vs. New: _hostbegin from bloomberg.com to 69.191.252.15
[x101 bloomberg.com] Old vs. New: new_IP from 0 to _none_

[x109 bing.com] Old vs. New: _hostbegin from 13.107.21.200 to 204.79.197.200

[x11 blogspot.com] Old vs. New: _hostbegin from blogspot.com to 172.217.10.9
[x11 blogspot.com] Old vs. New: new_IP from 0 to _none_

[x110 time.com] Old vs. New: _hostbegin from 99.84.181.88 to 99.84.178.24

[x112 google.it] Old vs. New: _hostbegin from google.it to 172.217.12.195
[x112 google.it] Old vs. New: new_IP from 0 to _none_

[x113 cdc.gov] Old vs. New: _hostbegin from cdc.gov to 198.246.102.49
[x113 cdc.gov] Old vs. New: new_IP from 0 to _none_

[x114 tripadvisor.com] Old vs. New: _hostbegin from tripadvisor.com to 192.229.189.15
[x114 tripadvisor.com] Old vs. New: new_IP from 0 to _none_

[x115 cpanel.net] Old vs. New: _hostbegin from cpanel.net to 208.74.123.84
[x115 cpanel.net] Old vs. New: new_IP from 0 to _none_

[x116 amazon.co.jp] Old vs. New: _hostbegin from 52.119.161.5 to 52.119.164.121

[x117 npr.org] Old vs. New: _hostbegin from npr.org to 216.35.221.76
[x117 npr.org] Old vs. New: new_IP from 0 to _none_

[x120 aol.com] Old vs. New: _hostbegin from aol.com to 106.10.218.150
[x120 aol.com] Old vs. New: new_IP from 0 to _none_

[x124 list-manage.com] Old vs. New: _hostbegin from list-manage.com to 205.201.132.96
[x124 list-manage.com] Old vs. New: new_IP from 0 to _none_

[x126 opera.com] Old vs. New: _hostbegin from opera.com to 185.26.182.103
[x126 opera.com] Old vs. New: new_IP from 0 to _none_

[x128 vkontakte.ru] Old vs. New: _hostbegin from 87.240.190.67 to 87.240.190.72

[x129 blogspot.co.uk] Old vs. New: _hostbegin from blogspot.co.uk to 172.217.10.137
[x129 blogspot.co.uk] Old vs. New: new_IP from 0 to _none_

[x13 adobe.com] Old vs. New: _hostbegin from 192.147.130.204 to 193.104.215.58

[x131 bandcamp.com] Old vs. New: _hostbegin from 151.101.193.28 to 151.101.1.28

[x132 apache.org] Old vs. New: _hostbegin from www.apache.org to 40.79.78.1
[x132 apache.org] Old vs. New: criticality from **M**  to **L** 
[x132 apache.org] Old vs. New: new_IP from 0 to _none_

[x133 bbc.com] Old vs. New: _hostbegin from 151.101.0.81 to 151.101.128.81

[x137 disqus.com] Old vs. New: _hostbegin from 151.101.192.134 to 151.101.64.134

[x138 behance.net] Old vs. New: _hostbegin from 151.101.193.197 to 151.101.1.197

[x139 mit.edu] Old vs. New: _hostbegin from 23.192.88.9 to 104.64.222.24

[x14 tumblr.com] Old vs. New: _hostbegin from tumblr.com to 74.114.154.17
[x14 tumblr.com] Old vs. New: new_IP from 0 to _none_

[x142 sina.com.cn] Old vs. New: _hostbegin from sina.com.cn to 123.126.157.222
[x142 sina.com.cn] Old vs. New: new_IP from 0 to _none_

[x145 google.es] Old vs. New: _hostbegin from google.es to 172.217.10.99
[x145 google.es] Old vs. New: new_IP from 0 to _none_

[x146 line.me] Old vs. New: _hostbegin from line.me to 203.104.138.138
[x146 line.me] Old vs. New: new_IP from 0 to _none_

[x147 wired.com] Old vs. New: _hostbegin from 151.101.2.194 to 151.101.66.194
... truncated to the first '500' lines.