msrT1notalphaaf
Member
- Messages
- 11
- Reaction score
- 2
- Points
- 3
hello fellow carders, i am having a bit of a problem running proxifier with a ABC S5 proxy ip, so from what i understand if you have 2 proxy services running on you´r device this will create a infinit loop between the 2 softwares, proxifier has a detection sistem to pervent this but when i hit to make a rule set to stop infinit loop it still does not work.
i ran, log> screen log> debug. and this is was the log that i got.
what can i do to fix this???? my chrome does not change my ip address
i ran, log> screen log> debug. and this is was the log that i got.
Code:
[11.26 12:51:18] Welcome to Proxifier v4.14 x64
[11.26 12:51:18] This trial version expires on December 24, 2025 (29 days left)
[11.26 12:51:18] Buy online: [URL="http://www.proxifier.com/buy/"]www.proxifier.com/buy/[/URL]
[11.26 12:51:18]
[11.26 12:51:18] Debug output enabled.
[11.26 12:51:18] Driver statistics: activeFlowCount=0, activeRedirectCount=0
[11.26 12:51:18] Proxifier Driver version 120 running
[11.26 12:51:18] Network Engine started.
[11.26 12:51:18] (Proxifier Update Checker) - Could not check for updates. No se ha encontrado el elemento..
[11.26 12:51:18] DNS cache cleared.
[11.26 12:51:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP self request: AF=2, Type=1, Name=iana.org
[11.26 12:51:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=iana.org, IP=192.0.43.8, ttl=3271
[11.26 12:51:42] proxychecker.exe (14232) - 34.124.190.108:8080 matching special module rule : direct connection
[11.26 12:51:46] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:03] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:03] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=api-eu1.hubspot.com
[11.26 12:52:03] svchost.exe (1216) - api-eu1.hubspot.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:03] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=[URL="http://www.google.com"]www.google.com[/URL]
[11.26 12:52:03] svchost.exe (1216) - [URL="http://www.google.com"]www.google.com[/URL] resolve via 192.168.101.1:53 : DNS
[11.26 12:52:03] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=api-eu1.hubspot.com, IP=172.65.202.85, ttl=144
[11.26 12:52:03] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.google.com"]www.google.com[/URL], IP=172.217.30.164, ttl=256
[11.26 12:52:03] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=beacons.gcp.gvt2.com
[11.26 12:52:03] svchost.exe (1216) - beacons.gcp.gvt2.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:03] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=beacons.gcp.gvt2.com, IP=142.251.133.131, ttl=46
[11.26 12:52:03] chrome.exe (7776) - beacons.gcp.gvt2.com(142.251.133.131):443 (UDP) : direct connection
[11.26 12:52:03] chrome.exe (7776) - beacons.gcp.gvt2.com(142.251.133.131):443 (UDP) : direct connection
[11.26 12:52:09] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:09] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=us-i-posthog.partytown.tripleten.com
[11.26 12:52:09] svchost.exe (1216) - us-i-posthog.partytown.tripleten.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:09] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=us-i-posthog.partytown.tripleten.com, IP=172.66.43.136, ttl=300
[11.26 12:52:09] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=us-i-posthog.partytown.tripleten.com, IP=172.66.40.120, ttl=300
[11.26 12:52:09] chrome.exe (7776) - us-i-posthog.partytown.tripleten.com(172.66.43.136):443 (UDP) : direct connection
[11.26 12:52:09] chrome.exe (7776) - us-i-posthog.partytown.tripleten.com(172.66.43.136):443 (UDP) : direct connection
[11.26 12:52:18] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=clients4.google.com
[11.26 12:52:18] svchost.exe (1216) - clients4.google.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=clients4.google.com, IP=172.217.162.142, ttl=27
[11.26 12:52:18] chrome.exe (7776) - clients4.google.com(172.217.162.142):443 (UDP) : direct connection
[11.26 12:52:18] chrome.exe (7776) - clients4.google.com(172.217.162.142):443 (UDP) : direct connection
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=tripleten.com
[11.26 12:52:24] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:24] svchost.exe (1216) - tripleten.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=track-eu1.hubspot.com
[11.26 12:52:24] svchost.exe (1216) - track-eu1.hubspot.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=tripleten.com, IP=172.66.40.120, ttl=300
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=tripleten.com, IP=172.66.43.136, ttl=300
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=optimizationguide-pa.googleapis.com
[11.26 12:52:24] svchost.exe (1216) - optimizationguide-pa.googleapis.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:24] chrome.exe (7776) - tripleten.com(172.66.40.120):443 (UDP) : direct connection
[11.26 12:52:24] chrome.exe (7776) - tripleten.com(172.66.40.120):443 (UDP) : direct connection
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=safebrowsing.google.com
[11.26 12:52:24] svchost.exe (1216) - safebrowsing.google.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=track-eu1.hubspot.com, IP=172.65.240.166, ttl=300
[11.26 12:52:24] chrome.exe (7776) - track-eu1.hubspot.com(172.65.240.166):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=172.217.30.202, ttl=176
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.251.133.138, ttl=176
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.251.129.202, ttl=176
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=172.217.162.106, ttl=176
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=172.217.28.106, ttl=176
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.250.218.202, ttl=176
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=172.217.29.10, ttl=176
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.251.133.106, ttl=176
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.251.132.10, ttl=176
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=172.217.30.170, ttl=176
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.251.132.170, ttl=176
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=172.217.162.138, ttl=176
[11.26 12:52:24] chrome.exe (7776) - optimizationguide-pa.googleapis.com(172.217.30.202):443 (UDP) : direct connection
[11.26 12:52:24] chrome.exe (7776) - optimizationguide-pa.googleapis.com(172.217.30.202):443 (UDP) : direct connection
[11.26 12:52:24] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=safebrowsing.google.com, IP=142.251.133.110, ttl=143
[11.26 12:52:24] chrome.exe (7776) - safebrowsing.google.com(142.251.133.110):443 (UDP) : direct connection
[11.26 12:52:24] chrome.exe (7776) - safebrowsing.google.com(142.251.133.110):443 (UDP) : direct connection
[11.26 12:52:24] chrome.exe (7776) - track-eu1.hubspot.com(172.65.240.166):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:25] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:26] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=b1.nel.goog
[11.26 12:52:26] svchost.exe (1216) - b1.nel.goog resolve via 192.168.101.1:53 : DNS
[11.26 12:52:26] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=b1.nel.goog, IP=142.251.132.163, ttl=296
[11.26 12:52:26] chrome.exe (7776) - b1.nel.goog(142.251.132.163):443 (UDP) : direct connection
[11.26 12:52:26] chrome.exe (7776) - b1.nel.goog(142.251.132.163):443 (UDP) : direct connection
[11.26 12:52:27] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:27] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=sentry-api.tripleten.com
[11.26 12:52:27] svchost.exe (1216) - sentry-api.tripleten.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:27] chrome.exe (7776) - tripleten.com(172.66.43.136):443 (UDP) : direct connection
[11.26 12:52:27] chrome.exe (7776) - tripleten.com(172.66.43.136):443 (UDP) : direct connection
[11.26 12:52:27] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=d2jcw3k6onjdla.cloudfront.net
[11.26 12:52:27] svchost.exe (1216) - d2jcw3k6onjdla.cloudfront.net resolve via 192.168.101.1:53 : DNS
[11.26 12:52:27] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=l.getsitecontrol.com
[11.26 12:52:27] svchost.exe (1216) - l.getsitecontrol.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:27] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=js-eu1.hs-scripts.com
[11.26 12:52:27] svchost.exe (1216) - js-eu1.hs-scripts.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:27] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=sentry-api.tripleten.com, IP=172.66.40.120, ttl=300
[11.26 12:52:27] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=sentry-api.tripleten.com, IP=172.66.43.136, ttl=300
[11.26 12:52:27] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:27] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=d2jcw3k6onjdla.cloudfront.net, IP=3.174.240.120, ttl=60
[11.26 12:52:27] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=d2jcw3k6onjdla.cloudfront.net, IP=3.174.240.146, ttl=60
[11.26 12:52:27] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=d2jcw3k6onjdla.cloudfront.net, IP=3.174.240.98, ttl=60
[11.26 12:52:27] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=d2jcw3k6onjdla.cloudfront.net, IP=3.174.240.93, ttl=60
[11.26 12:52:27] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:27] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:27] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:27] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:27] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:27] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=l.getsitecontrol.com, IP=200.25.11.8, ttl=35
[11.26 12:52:27] chrome.exe (7776) - l.getsitecontrol.com(200.25.11.8):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:27] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=js-eu1.hs-scripts.com, IP=172.65.208.22, ttl=300
[11.26 12:52:27] chrome.exe (7776) - js-eu1.hs-scripts.com(172.65.208.22):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:28] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:28] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:28] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:28] chrome.exe (7776) - l.getsitecontrol.com(200.25.11.8):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:28] chrome.exe (7776) - js-eu1.hs-scripts.com(172.65.208.22):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:28] chrome.exe (7776) - track-eu1.hubspot.com(172.65.240.166):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:29] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:29] chrome.exe (7776) - track-eu1.hubspot.com(172.65.240.166):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:29] chrome.exe (7776) - l.getsitecontrol.com(200.25.11.8):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:29] chrome.exe (7776) - js-eu1.hs-scripts.com(172.65.208.22):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:30] chrome.exe (7776) - js-eu1.hs-scripts.com(172.65.208.22):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:30] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:31] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:31] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:31] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:32] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:32] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:32] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 close, 1739 bytes (1.69 KB) sent, 2988 bytes (2.91 KB) received, lifetime <1 sec
[11.26 12:52:32] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 error : A connection request was canceled before the completion.
[11.26 12:52:32] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:32] chrome.exe (7776) - l.getsitecontrol.com(200.25.11.8):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:32] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 close, 1739 bytes (1.69 KB) sent, 0 bytes received, lifetime <1 sec
[11.26 12:52:33] chrome.exe (7776) - l.getsitecontrol.com(200.25.11.8):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:34] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:36] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:37] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:38] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=js-eu1.hs-analytics.net
[11.26 12:52:38] svchost.exe (1216) - js-eu1.hs-analytics.net resolve via 192.168.101.1:53 : DNS
[11.26 12:52:38] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=js-eu1.hscollectedforms.net
[11.26 12:52:38] svchost.exe (1216) - js-eu1.hscollectedforms.net resolve via 192.168.101.1:53 : DNS
[11.26 12:52:38] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=js-eu1.usemessages.com
[11.26 12:52:38] svchost.exe (1216) - js-eu1.usemessages.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:38] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=js-eu1.hs-banner.com
[11.26 12:52:38] svchost.exe (1216) - js-eu1.hs-banner.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:38] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=js-eu1.usemessages.com, IP=141.101.90.96, ttl=300
[11.26 12:52:38] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=js-eu1.usemessages.com, IP=141.101.90.97, ttl=300
[11.26 12:52:38] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=js-eu1.usemessages.com, IP=141.101.90.98, ttl=300
[11.26 12:52:38] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=js-eu1.usemessages.com, IP=141.101.90.99, ttl=300
[11.26 12:52:38] chrome.exe (7776) - js-eu1.usemessages.com(141.101.90.96):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:38] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=js-eu1.hs-banner.com, IP=172.65.202.201, ttl=300
[11.26 12:52:38] chrome.exe (7776) - js-eu1.hs-banner.com(172.65.202.201):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:38] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=js-eu1.hs-analytics.net, IP=172.65.238.60, ttl=300
[11.26 12:52:38] chrome.exe (7776) - js-eu1.hs-analytics.net(172.65.238.60):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:38] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=js-eu1.hscollectedforms.net, IP=172.65.192.122, ttl=300
[11.26 12:52:38] chrome.exe (7776) - js-eu1.hscollectedforms.net(172.65.192.122):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:38] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:38] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:38] chrome.exe (7776) - js-eu1.usemessages.com(141.101.90.96):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:38] chrome.exe (7776) - js-eu1.hs-banner.com(172.65.202.201):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:38] chrome.exe (7776) - js-eu1.hs-analytics.net(172.65.238.60):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:38] chrome.exe (7776) - js-eu1.hscollectedforms.net(172.65.192.122):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:39] chrome.exe (7776) - js-eu1.usemessages.com(141.101.90.96):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:40] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:40] chrome.exe (7776) - js-eu1.hs-banner.com(172.65.202.201):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:40] chrome.exe (7776) - l.getsitecontrol.com(200.25.11.8):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:40] chrome.exe (7776) - js-eu1.hs-analytics.net(172.65.238.60):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:40] chrome.exe (7776) - l.getsitecontrol.com(200.25.11.8):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:40] chrome.exe (7776) - js-eu1.hscollectedforms.net(172.65.192.122):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:41] chrome.exe (7776) - js-eu1.hs-analytics.net(172.65.238.60):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:41] chrome.exe (7776) - js-eu1.usemessages.com(141.101.90.96):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:42] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:43] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:43] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=forms-eu1.hscollectedforms.net
[11.26 12:52:43] svchost.exe (1216) - forms-eu1.hscollectedforms.net resolve via 192.168.101.1:53 : DNS
[11.26 12:52:43] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=forms-eu1.hscollectedforms.net, IP=172.65.192.122, ttl=300
[11.26 12:52:44] chrome.exe (7776) - js-eu1.hscollectedforms.net(172.65.192.122):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:46] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:46] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 close, 4060 bytes (3.96 KB) sent, 4376 bytes (4.27 KB) received, lifetime <1 sec
[11.26 12:52:47] chrome.exe (7776) - js-eu1.hs-banner.com(172.65.202.201):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:47] chrome.exe (7776) - l.getsitecontrol.com(200.25.11.8):443 close, 2412 bytes (2.35 KB) sent, 6456 bytes (6.30 KB) received, lifetime <1 sec
[11.26 12:52:48] chrome.exe (7776) - l.getsitecontrol.com(200.25.11.8):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:52:50] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:50] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 (UDP) : direct connection
[11.26 12:52:50] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 (UDP) : direct connection
[11.26 12:52:50] chrome.exe (7776) - track-eu1.hubspot.com(172.65.240.166):443 close, 3774 bytes (3.68 KB) sent, 2996 bytes (2.92 KB) received, lifetime <1 sec
[11.26 12:52:50] chrome.exe (7776) - js-eu1.hs-scripts.com(172.65.208.22):443 close, 2630 bytes (2.56 KB) sent, 5034 bytes (4.91 KB) received, lifetime <1 sec
[11.26 12:52:50] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=practicum-content.s3.amazonaws.com
[11.26 12:52:50] svchost.exe (1216) - practicum-content.s3.amazonaws.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:50] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 (UDP) : direct connection
[11.26 12:52:50] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 (UDP) : direct connection
[11.26 12:52:50] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=practicum-content.s3.amazonaws.com, IP=16.15.0.132, ttl=5
[11.26 12:52:50] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=practicum-content.s3.amazonaws.com, IP=52.219.193.161, ttl=5
[11.26 12:52:50] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=practicum-content.s3.amazonaws.com, IP=52.219.221.17, ttl=5
[11.26 12:52:50] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=practicum-content.s3.amazonaws.com, IP=16.15.0.245, ttl=5
[11.26 12:52:50] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=practicum-content.s3.amazonaws.com, IP=52.219.117.153, ttl=5
[11.26 12:52:50] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=practicum-content.s3.amazonaws.com, IP=16.15.4.112, ttl=5
[11.26 12:52:50] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=practicum-content.s3.amazonaws.com, IP=16.15.4.109, ttl=5
[11.26 12:52:50] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=practicum-content.s3.amazonaws.com, IP=16.15.4.47, ttl=5
[11.26 12:52:50] chrome.exe (7776) - js-eu1.hs-scripts.com(172.65.208.22):443 close, 2034 bytes (1.98 KB) sent, 3895 bytes (3.80 KB) received, lifetime <1 sec
[11.26 12:52:50] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 close, 2037 bytes (1.98 KB) sent, 4004 bytes (3.91 KB) received, lifetime <1 sec
[11.26 12:52:50] chrome.exe (7776) - track-eu1.hubspot.com(172.65.240.166):443 close, 2066 bytes (2.01 KB) sent, 1812 bytes (1.76 KB) received, lifetime <1 sec
[11.26 12:52:50] chrome.exe (7776) - practicum-content.s3.amazonaws.com(16.15.0.132):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:50] chrome.exe (7776) - practicum-content.s3.amazonaws.com(16.15.0.132):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:51] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:52] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:53] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:55] chrome.exe (7776) - practicum-content.s3.amazonaws.com(16.15.0.132):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:57] chrome.exe (7776) - js-eu1.hs-banner.com(172.65.202.201):443 close, 2729 bytes (2.66 KB) sent, 5517 bytes (5.38 KB) received, lifetime <1 sec
[11.26 12:52:58] chrome.exe (7776) - js-eu1.hs-analytics.net(172.65.238.60):443 close, 2657 bytes (2.59 KB) sent, 30471 bytes (29.7 KB) received, lifetime <1 sec
[11.26 12:52:58] chrome.exe (7776) - js-eu1.usemessages.com(141.101.90.96):443 close, 2730 bytes (2.66 KB) sent, 4756 bytes (4.64 KB) received, lifetime <1 sec
[11.26 12:52:58] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:52:58] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=s2.getsitecontrol.com
[11.26 12:52:58] svchost.exe (1216) - s2.getsitecontrol.com resolve via 192.168.101.1:53 : DNS
[11.26 12:52:58] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=s2.getsitecontrol.com, IP=195.181.163.196, ttl=35
[11.26 12:52:58] chrome.exe (7776) - js-eu1.hs-analytics.net(172.65.238.60):443 close, 2100 bytes (2.05 KB) sent, 3928 bytes (3.83 KB) received, lifetime <1 sec
[11.26 12:52:58] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 close, 1899 bytes (1.85 KB) sent, 7320 bytes (7.14 KB) received, lifetime <1 sec
[11.26 12:52:58] chrome.exe (7776) - l.getsitecontrol.com(200.25.11.8):443 close, 2193 bytes (2.14 KB) sent, 254 bytes received, lifetime <1 sec
[11.26 12:52:58] chrome.exe (7776) - s2.getsitecontrol.com(195.181.163.196):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:52:58] chrome.exe (7776) - s2.getsitecontrol.com(195.181.163.196):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:01] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 close, 3080 bytes (3.00 KB) sent, 284584 bytes (277 KB) received, lifetime <1 sec
[11.26 12:53:01] chrome.exe (7776) - js-eu1.hscollectedforms.net(172.65.192.122):443 close, 2919 bytes (2.85 KB) sent, 3151 bytes (3.07 KB) received, lifetime <1 sec
[11.26 12:53:02] chrome.exe (7776) - s2.getsitecontrol.com(195.181.163.196):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:02] chrome.exe (7776) - practicum-content.s3.amazonaws.com(16.15.0.132):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:04] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 close, 2928 bytes (2.85 KB) sent, 1205324 bytes (1.14 MB) received, lifetime <1 sec
[11.26 12:53:05] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:53:06] dashost.exe (3780, System) - 192.168.101.7:60000 system connection bypassed
[11.26 12:53:07] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:53:08] chrome.exe (7776) - s2.getsitecontrol.com(195.181.163.196):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:08] dashost.exe (3780, System) - 192.168.101.7:60000 system connection bypassed
[11.26 12:53:09] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:53:09] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=events.getsitectrl.com
[11.26 12:53:09] svchost.exe (1216) - events.getsitectrl.com resolve via 192.168.101.1:53 : DNS
[11.26 12:53:09] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=events.getsitectrl.com, IP=54.205.196.206, ttl=37
[11.26 12:53:09] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=events.getsitectrl.com, IP=52.86.215.97, ttl=37
[11.26 12:53:09] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=events.getsitectrl.com, IP=13.216.86.129, ttl=37
[11.26 12:53:09] chrome.exe (7776) - d2jcw3k6onjdla.cloudfront.net(3.174.240.120):443 close, 1988 bytes (1.94 KB) sent, 1563 bytes (1.52 KB) received, lifetime <1 sec
[11.26 12:53:09] chrome.exe (7776) - js-eu1.hs-banner.com(172.65.202.201):443 close, 2097 bytes (2.04 KB) sent, 3904 bytes (3.81 KB) received, lifetime <1 sec
[11.26 12:53:09] chrome.exe (7776) - js-eu1.hscollectedforms.net(172.65.192.122):443 close, 2104 bytes (2.05 KB) sent, 3936 bytes (3.84 KB) received, lifetime <1 sec
[11.26 12:53:09] chrome.exe (7776) - js-eu1.usemessages.com(141.101.90.96):443 close, 2099 bytes (2.04 KB) sent, 3926 bytes (3.83 KB) received, lifetime <1 sec
[11.26 12:53:09] chrome.exe (7776) - events.getsitectrl.com(54.205.196.206):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:10] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:53:10] chrome.exe (7776) - events.getsitectrl.com(54.205.196.206):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:11] chrome.exe (7776) - events.getsitectrl.com(54.205.196.206):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:13] chrome.exe (7776) - l.getsitecontrol.com(200.25.11.8):443 close, 2494 bytes (2.43 KB) sent, 26434 bytes (25.8 KB) received, lifetime <1 sec
[11.26 12:53:13] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:53:22] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:53:23] chrome.exe (7776) - events.getsitectrl.com(54.205.196.206):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:24] chrome.exe (7776) - s2.getsitecontrol.com(195.181.163.196):443 close, 2466 bytes (2.40 KB) sent, 61561 bytes (60.1 KB) received, lifetime <1 sec
[11.26 12:53:26] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:53:26] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=a.nel.cloudflare.com
[11.26 12:53:26] svchost.exe (1216) - a.nel.cloudflare.com resolve via 192.168.101.1:53 : DNS
[11.26 12:53:26] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=a.nel.cloudflare.com, IP=35.190.80.1, ttl=2163
[11.26 12:53:26] chrome.exe (7776) - a.nel.cloudflare.com(35.190.80.1):443 (UDP) : direct connection
[11.26 12:53:26] chrome.exe (7776) - a.nel.cloudflare.com(35.190.80.1):443 (UDP) : direct connection
[11.26 12:53:26] chrome.exe (7776) - practicum-content.s3.amazonaws.com(16.15.0.132):443 close, 1904 bytes (1.85 KB) sent, 5995 bytes (5.85 KB) received, lifetime <1 sec
[11.26 12:53:26] chrome.exe (7776) - a.nel.cloudflare.com(35.190.80.1):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:28] chrome.exe (7776) - events.getsitectrl.com(54.205.196.206):443 close, 2469 bytes (2.41 KB) sent, 5422 bytes (5.29 KB) received, lifetime <1 sec
[11.26 12:53:29] chrome.exe (7776) - a.nel.cloudflare.com(35.190.80.1):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:35] msedgewebview2.exe (5300) - [2603:1020:201:10::10f]:443 (UDP) (IPv6) : direct connection
[11.26 12:53:35] msedgewebview2.exe (5300) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=config.edge.skype.com
[11.26 12:53:35] msedgewebview2.exe (5300) - config.edge.skype.com resolve via 192.168.101.1:53 : DNS
[11.26 12:53:35] msedgewebview2.exe (5300) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=cc7-31b1d1f0-9605-438f-8709-f63f4b9828fb.example
[11.26 12:53:35] msedgewebview2.exe (5300) - cc7-31b1d1f0-9605-438f-8709-f63f4b9828fb.example resolve via 192.168.101.1:53 : DNS
[11.26 12:53:35] msedgewebview2.exe (5300) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=config.edge.skype.com, IP=150.171.22.17, ttl=18
[11.26 12:53:35] msedgewebview2.exe (5300) - config.edge.skype.com(150.171.22.17):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:35] msedgewebview2.exe (5300) - 192.168.101.1:53 DNS-UDP empty response: AF=2, Name=cc7-31b1d1f0-9605-438f-8709-f63f4b9828fb.example
[11.26 12:53:35] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=cc7-31b1d1f0-9605-438f-8709-f63f4b9828fb.example
[11.26 12:53:35] svchost.exe (1216) - cc7-31b1d1f0-9605-438f-8709-f63f4b9828fb.example resolve via 192.168.101.1:53 : DNS
[11.26 12:53:35] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP empty response: AF=2, Name=cc7-31b1d1f0-9605-438f-8709-f63f4b9828fb.example
[11.26 12:53:36] msedgewebview2.exe (5300) - config.edge.skype.com(150.171.22.17):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:37] msedgewebview2.exe (5300) - [2603:1020:201:10::10f]:443 (UDP) (IPv6) : direct connection
[11.26 12:53:37] msedgewebview2.exe (5300) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=ipm-provider.ff.avast.com
[11.26 12:53:37] msedgewebview2.exe (5300) - ipm-provider.ff.avast.com resolve via 192.168.101.1:53 : DNS
[11.26 12:53:37] msedgewebview2.exe (5300) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ipm-provider.ff.avast.com, IP=34.111.24.1, ttl=633
[11.26 12:53:37] msedgewebview2.exe (5300) - ipm-provider.ff.avast.com(34.111.24.1):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:37] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:53:37] msedgewebview2.exe (5300) - ipm-provider.ff.avast.com(34.111.24.1):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:38] msedgewebview2.exe (5300) - config.edge.skype.com(150.171.22.17):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:39] msedgewebview2.exe (5300) - ipm-provider.ff.avast.com(34.111.24.1):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:53:39] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=mobile.events.data.microsoft.com
[11.26 12:53:39] svchost.exe (1216) - mobile.events.data.microsoft.com resolve via 192.168.101.1:53 : DNS
[11.26 12:53:39] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=mobile.events.data.microsoft.com, IP=51.104.15.252, ttl=10
[11.26 12:53:39] mpdefendercoreservice.exe (4944, System) - mobile.events.data.microsoft.com(51.104.15.252):443 system connection bypassed
[11.26 12:53:40] msedgewebview2.exe (5300) - ipm-provider.ff.avast.com(34.111.24.1):443 close, 1799 bytes (1.75 KB) sent, 0 bytes received, lifetime <1 sec
[11.26 12:53:42] msedgewebview2.exe (5300) - config.edge.skype.com(150.171.22.17):443 close, 2575 bytes (2.51 KB) sent, 7060 bytes (6.89 KB) received, lifetime <1 sec
[11.26 12:53:43] msedgewebview2.exe (5300) - ipm-provider.ff.avast.com(34.111.24.1):443 error : A connection request was canceled before the completion.
[11.26 12:53:51] msedgewebview2.exe (5300) - config.edge.skype.com(150.171.22.17):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:53:52] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:00] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:00] chrome.exe (7776) - sentry-api.tripleten.com(172.66.43.136):443 (UDP) : direct connection
[11.26 12:54:00] chrome.exe (7776) - sentry-api.tripleten.com(172.66.43.136):443 (UDP) : direct connection
[11.26 12:54:03] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:07] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:08] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:13] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:16] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:19] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:19] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 (UDP) : direct connection
[11.26 12:54:19] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 (UDP) : direct connection
[11.26 12:54:19] chrome.exe (7776) - www.google.com(172.217.30.164):443 (UDP) : direct connection
[11.26 12:54:19] chrome.exe (7776) - www.google.com(172.217.30.164):443 (UDP) : direct connection
[11.26 12:54:19] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 (UDP) : direct connection
[11.26 12:54:19] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 (UDP) : direct connection
[11.26 12:54:21] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:23] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:28] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:34] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=analytics.avcdn.net
[11.26 12:54:34] svchost.exe (1216) - analytics.avcdn.net resolve via 192.168.101.1:53 : DNS
[11.26 12:54:34] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=analytics.avcdn.net, IP=34.117.223.223, ttl=1151
[11.26 12:54:34] ccleaner_service.exe (4644, System) - analytics.avcdn.net(34.117.223.223):443 system connection bypassed
[11.26 12:54:34] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:34] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=clients4.google.com
[11.26 12:54:34] svchost.exe (1216) - clients4.google.com resolve via 192.168.101.1:53 : DNS
[11.26 12:54:34] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=clients4.google.com, IP=172.217.30.174, ttl=101
[11.26 12:54:34] chrome.exe (7776) - clients4.google.com(172.217.30.174):443 (UDP) : direct connection
[11.26 12:54:34] chrome.exe (7776) - clients4.google.com(172.217.30.174):443 (UDP) : direct connection
[11.26 12:54:39] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:46] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:48] chrome.exe (7776) - practicum-content.s3.amazonaws.com(16.15.0.132):443 close, 2553 bytes (2.49 KB) sent, 1009521 bytes (985 KB) received, lifetime <1 sec
[11.26 12:54:48] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:48] chrome.exe (7776) - a.nel.cloudflare.com(35.190.80.1):443 close, 2118 bytes (2.06 KB) sent, 5183 bytes (5.06 KB) received, lifetime <1 sec
[11.26 12:54:48] chrome.exe (7776) - events.getsitectrl.com(54.205.196.206):443 close, 2013 bytes (1.96 KB) sent, 475 bytes received, lifetime <1 sec
[11.26 12:54:48] chrome.exe (7776) - s2.getsitecontrol.com(195.181.163.196):443 close, 2226 bytes (2.17 KB) sent, 619 bytes received, lifetime <1 sec
[11.26 12:54:48] chrome.exe (7776) - track-eu1.hubspot.com(172.65.240.166):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:54:48] chrome.exe (7776) - track-eu1.hubspot.com(172.65.240.166):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:54:54] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:55] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:54:57] System (4, System) - 192.168.101.255:138 (UDP) : direct connection
[11.26 12:54:58] chrome.exe (7776) - track-eu1.hubspot.com(172.65.240.166):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:55:01] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:55:02] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:55:03] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:55:05] chrome.exe (7776) - track-eu1.hubspot.com(172.65.240.166):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:55:10] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:55:10] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=api-eu1.hubspot.com
[11.26 12:55:10] svchost.exe (1216) - api-eu1.hubspot.com resolve via 192.168.101.1:53 : DNS
[11.26 12:55:10] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=api-eu1.hubspot.com, IP=172.65.202.85, ttl=300
[11.26 12:55:17] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:55:18] chrome.exe (7776) - track-eu1.hubspot.com(172.65.240.166):443 close, 3007 bytes (2.93 KB) sent, 5084 bytes (4.96 KB) received, lifetime <1 sec
[11.26 12:55:46] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:55:54] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:55:54] chrome.exe (7776) - sentry-api.tripleten.com(172.66.43.136):443 (UDP) : direct connection
[11.26 12:55:54] chrome.exe (7776) - sentry-api.tripleten.com(172.66.43.136):443 (UDP) : direct connection
[11.26 12:56:02] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:02] chrome.exe (7776) - www.google.com(172.217.30.164):443 (UDP) : direct connection
[11.26 12:56:02] chrome.exe (7776) - www.google.com(172.217.30.164):443 (UDP) : direct connection
[11.26 12:56:02] chrome.exe (7776) - www.google.com(172.217.30.164):443 (UDP) : direct connection
[11.26 12:56:02] chrome.exe (7776) - www.google.com(172.217.30.164):443 (UDP) : direct connection
[11.26 12:56:02] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=lh3.google.com
[11.26 12:56:02] svchost.exe (1216) - lh3.google.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:02] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=lh3.google.com, IP=142.251.128.14, ttl=212
[11.26 12:56:02] chrome.exe (7776) - lh3.google.com(142.251.128.14):443 (UDP) : direct connection
[11.26 12:56:02] chrome.exe (7776) - lh3.google.com(142.251.128.14):443 (UDP) : direct connection
[11.26 12:56:02] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=ogads-pa.clients6.google.com
[11.26 12:56:02] svchost.exe (1216) - ogads-pa.clients6.google.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:02] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ogads-pa.clients6.google.com, IP=172.217.30.202, ttl=119
[11.26 12:56:02] chrome.exe (7776) - ogads-pa.clients6.google.com(172.217.30.202):443 (UDP) : direct connection
[11.26 12:56:02] chrome.exe (7776) - ogads-pa.clients6.google.com(172.217.30.202):443 (UDP) : direct connection
[11.26 12:56:02] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=wpad.bbrouter
[11.26 12:56:02] svchost.exe (1216) - wpad.bbrouter resolve via 192.168.101.1:53 : DNS
[11.26 12:56:02] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=wpad.bbrouter
[11.26 12:56:02] svchost.exe (1216) - wpad.bbrouter resolve via 192.168.101.1:53 : DNS
[11.26 12:56:02] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP empty response: AF=2, Name=wpad.bbrouter
[11.26 12:56:02] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP empty response: AF=2, Name=wpad.bbrouter
[11.26 12:56:02] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=lh3.googleusercontent.com
[11.26 12:56:02] svchost.exe (1216) - lh3.googleusercontent.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:02] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=lh3.googleusercontent.com, IP=172.217.29.1, ttl=7
[11.26 12:56:02] chrome.exe (7776) - lh3.googleusercontent.com(172.217.29.1):443 (UDP) : direct connection
[11.26 12:56:02] chrome.exe (7776) - lh3.googleusercontent.com(172.217.29.1):443 (UDP) : direct connection
[11.26 12:56:02] chrome.exe (7776) - ogads-pa.clients6.google.com(172.217.30.202):443 (UDP) : direct connection
[11.26 12:56:02] chrome.exe (7776) - ogads-pa.clients6.google.com(172.217.30.202):443 (UDP) : direct connection
[11.26 12:56:03] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:03] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=encrypted-tbn0.gstatic.com
[11.26 12:56:03] svchost.exe (1216) - encrypted-tbn0.gstatic.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:03] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=encrypted-tbn0.gstatic.com, IP=142.251.133.110, ttl=203
[11.26 12:56:03] chrome.exe (7776) - encrypted-tbn0.gstatic.com(142.251.133.110):443 (UDP) : direct connection
[11.26 12:56:03] chrome.exe (7776) - encrypted-tbn0.gstatic.com(142.251.133.110):443 (UDP) : direct connection
[11.26 12:56:03] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=play.google.com
[11.26 12:56:03] svchost.exe (1216) - play.google.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:03] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=play.google.com, IP=172.217.162.142, ttl=213
[11.26 12:56:03] chrome.exe (7776) - play.google.com(172.217.162.142):443 (UDP) : direct connection
[11.26 12:56:03] chrome.exe (7776) - play.google.com(172.217.162.142):443 (UDP) : direct connection
[11.26 12:56:03] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=optimizationguide-pa.googleapis.com
[11.26 12:56:03] svchost.exe (1216) - optimizationguide-pa.googleapis.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:03] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=fonts.gstatic.com
[11.26 12:56:03] svchost.exe (1216) - fonts.gstatic.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.250.218.202, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=172.217.30.170, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=172.217.30.202, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.251.132.10, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.251.129.202, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.251.133.106, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.251.132.170, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.250.219.170, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=172.217.29.10, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=172.217.162.138, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.251.128.10, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=142.251.133.138, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=172.217.162.106, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimizationguide-pa.googleapis.com, IP=172.217.28.106, ttl=162
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=fonts.gstatic.com, IP=172.217.30.195, ttl=133
[11.26 12:56:04] chrome.exe (7776) - optimizationguide-pa.googleapis.com(142.250.218.202):443 (UDP) : direct connection
[11.26 12:56:04] chrome.exe (7776) - optimizationguide-pa.googleapis.com(142.250.218.202):443 (UDP) : direct connection
[11.26 12:56:04] chrome.exe (7776) - fonts.gstatic.com(172.217.30.195):443 (UDP) : direct connection
[11.26 12:56:04] chrome.exe (7776) - fonts.gstatic.com(172.217.30.195):443 (UDP) : direct connection
[11.26 12:56:04] chrome.exe (7776) - lh3.google.com(142.251.128.14):443 (UDP) : direct connection
[11.26 12:56:04] chrome.exe (7776) - lh3.google.com(142.251.128.14):443 (UDP) : direct connection
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=[URL="http://www.googleadservices.com"]www.googleadservices.com[/URL]
[11.26 12:56:04] svchost.exe (1216) - [URL="http://www.googleadservices.com"]www.googleadservices.com[/URL] resolve via 192.168.101.1:53 : DNS
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.googleadservices.com"]www.googleadservices.com[/URL], IP=142.251.133.98, ttl=46
[11.26 12:56:04] chrome.exe (7776) - www.googleadservices.com(142.251.133.98):443 (UDP) : direct connection
[11.26 12:56:04] chrome.exe (7776) - www.googleadservices.com(142.251.133.98):443 (UDP) : direct connection
[11.26 12:56:04] chrome.exe (7776) - lh3.googleusercontent.com(172.217.29.1):443 (UDP) : direct connection
[11.26 12:56:04] chrome.exe (7776) - lh3.googleusercontent.com(172.217.29.1):443 (UDP) : direct connection
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=[URL="http://www.googletagmanager.com"]www.googletagmanager.com[/URL]
[11.26 12:56:04] svchost.exe (1216) - [URL="http://www.googletagmanager.com"]www.googletagmanager.com[/URL] resolve via 192.168.101.1:53 : DNS
[11.26 12:56:04] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.googletagmanager.com"]www.googletagmanager.com[/URL], IP=172.217.30.168, ttl=254
[11.26 12:56:04] chrome.exe (7776) - www.googletagmanager.com(172.217.30.168):443 (UDP) : direct connection
[11.26 12:56:04] chrome.exe (7776) - www.googletagmanager.com(172.217.30.168):443 (UDP) : direct connection
[11.26 12:56:04] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:04] chrome.exe (7776) - optimizationguide-pa.googleapis.com(172.217.30.202):443 (UDP) : direct connection
[11.26 12:56:04] chrome.exe (7776) - optimizationguide-pa.googleapis.com(172.217.30.202):443 (UDP) : direct connection
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=accounts.google.com
[11.26 12:56:05] svchost.exe (1216) - accounts.google.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] chrome.exe (7776) - encrypted-tbn0.gstatic.com(142.251.133.110):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - encrypted-tbn0.gstatic.com(142.251.133.110):443 (UDP) : direct connection
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=accounts.google.com, IP=74.125.139.84, ttl=144
[11.26 12:56:05] chrome.exe (7776) - accounts.google.com(74.125.139.84):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - accounts.google.com(74.125.139.84):443 (UDP) : direct connection
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL]
[11.26 12:56:05] svchost.exe (1216) - [URL="http://www.youtube.com"]www.youtube.com[/URL] resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=172.217.162.142, ttl=291
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=172.217.30.174, ttl=291
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=172.217.30.206, ttl=291
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=142.251.132.174, ttl=291
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=142.250.218.206, ttl=291
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=172.217.28.110, ttl=291
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=172.217.162.110, ttl=291
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=142.251.133.142, ttl=291
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=142.251.129.206, ttl=291
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=142.251.132.14, ttl=291
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=172.217.29.14, ttl=291
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=142.251.133.110, ttl=291
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.youtube.com"]www.youtube.com[/URL], IP=142.251.128.14, ttl=291
[11.26 12:56:05] chrome.exe (7776) - www.youtube.com(172.217.162.142):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - www.youtube.com(172.217.162.142):443 (UDP) : direct connection
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=whatismyipaddress.com
[11.26 12:56:05] svchost.exe (1216) - whatismyipaddress.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=fonts.googleapis.com
[11.26 12:56:05] svchost.exe (1216) - fonts.googleapis.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=safebrowsing.google.com
[11.26 12:56:05] svchost.exe (1216) - safebrowsing.google.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=whatismyipaddress.com, IP=104.19.222.79, ttl=300
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=whatismyipaddress.com, IP=104.19.223.79, ttl=300
[11.26 12:56:05] chrome.exe (7776) - whatismyipaddress.com(104.19.222.79):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - whatismyipaddress.com(104.19.222.79):443 (UDP) : direct connection
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=a.omappapi.com
[11.26 12:56:05] svchost.exe (1216) - a.omappapi.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] chrome.exe (7776) - fonts.gstatic.com(172.217.30.195):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - fonts.gstatic.com(172.217.30.195):443 (UDP) : direct connection
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=app.fusebox.fm
[11.26 12:56:05] svchost.exe (1216) - app.fusebox.fm resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] chrome.exe (7776) - www.youtube.com(172.217.162.142):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - www.youtube.com(172.217.162.142):443 (UDP) : direct connection
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=fonts.googleapis.com, IP=172.217.30.170, ttl=76
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=safebrowsing.google.com, IP=142.251.129.206, ttl=35
[11.26 12:56:05] chrome.exe (7776) - safebrowsing.google.com(142.251.129.206):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - safebrowsing.google.com(142.251.129.206):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - fonts.googleapis.com(172.217.30.170):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - fonts.googleapis.com(172.217.30.170):443 (UDP) : direct connection
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=ds6.probe.whatismyipaddress.com
[11.26 12:56:05] svchost.exe (1216) - ds6.probe.whatismyipaddress.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=a.omappapi.com, IP=200.25.11.8, ttl=35
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=app.fusebox.fm, IP=104.26.13.133, ttl=300
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=app.fusebox.fm, IP=172.67.70.40, ttl=300
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=app.fusebox.fm, IP=104.26.12.133, ttl=300
[11.26 12:56:05] chrome.exe (7776) - app.fusebox.fm(104.26.13.133):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - app.fusebox.fm(104.26.13.133):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - track-eu1.hubspot.com(172.65.240.166):443 close, 2130 bytes (2.08 KB) sent, 3882 bytes (3.79 KB) received, lifetime <1 sec
[11.26 12:56:05] chrome.exe (7776) - a.omappapi.com(200.25.11.8):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=map1.whatismyipaddress.com
[11.26 12:56:05] svchost.exe (1216) - map1.whatismyipaddress.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=onesignal.com
[11.26 12:56:05] svchost.exe (1216) - onesignal.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP empty response: AF=2, Name=ds6.probe.whatismyipaddress.com
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=c.amazon-adsystem.com
[11.26 12:56:05] svchost.exe (1216) - c.amazon-adsystem.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=c.amazon-adsystem.com, IP=3.174.237.92, ttl=31
[11.26 12:56:05] chrome.exe (7776) - c.amazon-adsystem.com(3.174.237.92):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=a.pub.network
[11.26 12:56:05] svchost.exe (1216) - a.pub.network resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=map1.whatismyipaddress.com, IP=104.19.222.79, ttl=300
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=map1.whatismyipaddress.com, IP=104.19.223.79, ttl=300
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=onesignal.com, IP=104.17.111.223, ttl=300
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=onesignal.com, IP=104.16.160.145, ttl=300
[11.26 12:56:05] chrome.exe (7776) - onesignal.com(104.17.111.223):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - onesignal.com(104.17.111.223):443 (UDP) : direct connection
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=cdn.onesignal.com
[11.26 12:56:05] svchost.exe (1216) - cdn.onesignal.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=zipthelake.com
[11.26 12:56:05] svchost.exe (1216) - zipthelake.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] chrome.exe (7776) - www.youtube.com(172.217.162.142):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=a.pub.network, IP=104.18.21.206, ttl=160
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=a.pub.network, IP=104.18.20.206, ttl=160
[11.26 12:56:05] chrome.exe (7776) - fonts.gstatic.com(172.217.30.195):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - fonts.gstatic.com(172.217.30.195):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - app.fusebox.fm(104.26.13.133):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - app.fusebox.fm(104.26.13.133):443 (UDP) : direct connection
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cdn.onesignal.com, IP=104.17.111.223, ttl=300
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cdn.onesignal.com, IP=104.16.160.145, ttl=300
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=zipthelake.com, IP=34.110.146.185, ttl=30
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=cmp.inmobi.com
[11.26 12:56:05] svchost.exe (1216) - cmp.inmobi.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:05] chrome.exe (7776) - a.pub.network(104.18.21.206):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - www.googletagmanager.com(172.217.30.168):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - a.pub.network(104.18.21.206):443 (UDP) : direct connection
[11.26 12:56:05] chrome.exe (7776) - www.googletagmanager.com(172.217.30.168):443 (UDP) : direct connection
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cmp.inmobi.com, IP=18.155.252.127, ttl=60
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cmp.inmobi.com, IP=18.155.252.111, ttl=60
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cmp.inmobi.com, IP=18.155.252.97, ttl=60
[11.26 12:56:05] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cmp.inmobi.com, IP=18.155.252.2, ttl=60
[11.26 12:56:05] chrome.exe (7776) - cmp.inmobi.com(18.155.252.127):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=optimise.net
[11.26 12:56:06] svchost.exe (1216) - optimise.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=api.floors.dev
[11.26 12:56:06] svchost.exe (1216) - api.floors.dev resolve via 192.168.101.1:53 : DNS
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=d.pub.network
[11.26 12:56:06] svchost.exe (1216) - d.pub.network resolve via 192.168.101.1:53 : DNS
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=optimise.net, IP=34.111.152.239, ttl=14284
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=api.floors.dev, IP=34.160.128.112, ttl=143
[11.26 12:56:06] chrome.exe (7776) - api.floors.dev(34.160.128.112):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - api.floors.dev(34.160.128.112):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - optimise.net(34.111.152.239):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - optimise.net(34.111.152.239):443 (UDP) : direct connection
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=d.pub.network, IP=34.160.152.31, ttl=300
[11.26 12:56:06] chrome.exe (7776) - d.pub.network(34.160.152.31):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - d.pub.network(34.160.152.31):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - d.pub.network(34.160.152.31):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:06] chrome.exe (7776) - cmp.inmobi.com(18.155.252.127):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=api.omappapi.com
[11.26 12:56:06] svchost.exe (1216) - api.omappapi.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:06] chrome.exe (7776) - app.fusebox.fm(104.26.13.133):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - app.fusebox.fm(104.26.13.133):443 (UDP) : direct connection
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=static.adsafeprotected.com
[11.26 12:56:06] svchost.exe (1216) - static.adsafeprotected.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=api.omappapi.com, IP=104.18.3.9, ttl=300
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=api.omappapi.com, IP=104.18.2.9, ttl=300
[11.26 12:56:06] chrome.exe (7776) - api.omappapi.com(104.18.3.9):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=securepubads.g.doubleclick.net
[11.26 12:56:06] svchost.exe (1216) - securepubads.g.doubleclick.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:06] chrome.exe (7776) - optimise.net(34.111.152.239):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - optimise.net(34.111.152.239):443 (UDP) : direct connection
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=securepubads.g.doubleclick.net, IP=172.217.30.194, ttl=91
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=static.adsafeprotected.com, IP=3.166.181.107, ttl=60
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=static.adsafeprotected.com, IP=3.166.181.65, ttl=60
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=static.adsafeprotected.com, IP=3.166.181.14, ttl=60
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=static.adsafeprotected.com, IP=3.166.181.36, ttl=60
[11.26 12:56:06] chrome.exe (7776) - securepubads.g.doubleclick.net(172.217.30.194):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - securepubads.g.doubleclick.net(172.217.30.194):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - static.adsafeprotected.com(3.166.181.107):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:06] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:06] chrome.exe (7776) - optimise.net(34.111.152.239):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=[URL="http://www.clarity.ms"]www.clarity.ms[/URL]
[11.26 12:56:06] svchost.exe (1216) - [URL="http://www.clarity.ms"]www.clarity.ms[/URL] resolve via 192.168.101.1:53 : DNS
[11.26 12:56:06] chrome.exe (7776) - api.omappapi.com(104.18.3.9):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:06] chrome.exe (7776) - optimise.net(34.111.152.239):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - optimise.net(34.111.152.239):443 (UDP) : direct connection
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.clarity.ms"]www.clarity.ms[/URL], IP=4.153.187.221, ttl=6
[11.26 12:56:06] chrome.exe (7776) - www.clarity.ms(4.153.187.221):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:06] chrome.exe (7776) - cdn.onesignal.com(104.17.111.223):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - cdn.onesignal.com(104.17.111.223):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - optimise.net(34.111.152.239):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:06] chrome.exe (7776) - zipthelake.com(34.110.146.185):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - zipthelake.com(34.110.146.185):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - c.amazon-adsystem.com(3.174.237.92):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=[URL="http://www.googletagservices.com"]www.googletagservices.com[/URL]
[11.26 12:56:06] svchost.exe (1216) - [URL="http://www.googletagservices.com"]www.googletagservices.com[/URL] resolve via 192.168.101.1:53 : DNS
[11.26 12:56:06] chrome.exe (7776) - a.pub.network(104.18.21.206):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - a.pub.network(104.18.21.206):443 (UDP) : direct connection
[11.26 12:56:06] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.googletagservices.com"]www.googletagservices.com[/URL], IP=172.217.28.98, ttl=38
[11.26 12:56:06] chrome.exe (7776) - www.googletagservices.com(172.217.28.98):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - www.googletagservices.com(172.217.28.98):443 (UDP) : direct connection
[11.26 12:56:06] chrome.exe (7776) - www.clarity.ms(4.153.187.221):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:07] chrome.exe (7776) - c.amazon-adsystem.com(3.174.237.92):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:07] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=analytics.google.com
[11.26 12:56:07] svchost.exe (1216) - analytics.google.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:07] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=stats.g.doubleclick.net
[11.26 12:56:07] svchost.exe (1216) - stats.g.doubleclick.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:07] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=[URL="http://www.google.com.co"]www.google.com.co[/URL]
[11.26 12:56:07] svchost.exe (1216) - [URL="http://www.google.com.co"]www.google.com.co[/URL] resolve via 192.168.101.1:53 : DNS
[11.26 12:56:07] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=analytics.google.com, IP=172.217.162.142, ttl=197
[11.26 12:56:07] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=stats.g.doubleclick.net, IP=74.125.139.154, ttl=179
[11.26 12:56:07] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=stats.g.doubleclick.net, IP=74.125.139.157, ttl=179
[11.26 12:56:07] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=stats.g.doubleclick.net, IP=74.125.139.155, ttl=179
[11.26 12:56:07] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=stats.g.doubleclick.net, IP=74.125.139.156, ttl=179
[11.26 12:56:07] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=[URL="http://www.google.com.co"]www.google.com.co[/URL], IP=142.251.128.3, ttl=37
[11.26 12:56:07] chrome.exe (7776) - analytics.google.com(172.217.162.142):443 (UDP) : direct connection
[11.26 12:56:07] chrome.exe (7776) - www.google.com.co(142.251.128.3):443 (UDP) : direct connection
[11.26 12:56:07] chrome.exe (7776) - analytics.google.com(172.217.162.142):443 (UDP) : direct connection
[11.26 12:56:07] chrome.exe (7776) - www.google.com.co(142.251.128.3):443 (UDP) : direct connection
[11.26 12:56:07] chrome.exe (7776) - stats.g.doubleclick.net(74.125.139.154):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:07] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:07] chrome.exe (7776) - stats.g.doubleclick.net(74.125.139.154):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:10] chrome.exe (7776) - d.pub.network(34.160.152.31):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:12] chrome.exe (7776) - cmp.inmobi.com(18.155.252.127):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:12] chrome.exe (7776) - c.amazon-adsystem.com(3.174.237.92):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:13] chrome.exe (7776) - c.amazon-adsystem.com(3.174.237.92):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:13] chrome.exe (7776) - www.youtube.com(172.217.162.142):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:13] chrome.exe (7776) - a.omappapi.com(200.25.11.8):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:13] chrome.exe (7776) - api.omappapi.com(104.18.3.9):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:14] chrome.exe (7776) - api.omappapi.com(104.18.3.9):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:15] chrome.exe (7776) - stats.g.doubleclick.net(74.125.139.154):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:15] chrome.exe (7776) - optimise.net(34.111.152.239):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:16] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:16] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=css-tricks.com
[11.26 12:56:16] svchost.exe (1216) - css-tricks.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=css-tricks.com, IP=172.64.148.235, ttl=300
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=css-tricks.com, IP=104.18.39.21, ttl=300
[11.26 12:56:17] chrome.exe (7776) - css-tricks.com(172.64.148.235):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:17] chrome.exe (7776) - c.amazon-adsystem.com(3.174.237.92):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=config.aps.amazon-adsystem.com
[11.26 12:56:17] svchost.exe (1216) - config.aps.amazon-adsystem.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=live.primis.tech
[11.26 12:56:17] svchost.exe (1216) - live.primis.tech resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=config.aps.amazon-adsystem.com, IP=143.204.23.47, ttl=47
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=config.aps.amazon-adsystem.com, IP=143.204.23.26, ttl=47
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=config.aps.amazon-adsystem.com, IP=143.204.23.61, ttl=47
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=config.aps.amazon-adsystem.com, IP=143.204.23.45, ttl=47
[11.26 12:56:17] chrome.exe (7776) - config.aps.amazon-adsystem.com(143.204.23.47):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=cdn-ima.33across.com
[11.26 12:56:17] svchost.exe (1216) - cdn-ima.33across.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=secure.cdn.fastclick.net
[11.26 12:56:17] svchost.exe (1216) - secure.cdn.fastclick.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=cdn.id5-sync.com
[11.26 12:56:17] svchost.exe (1216) - cdn.id5-sync.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cdn-ima.33across.com, IP=127.0.0.1, ttl=17709
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=cdn-ima.33across.com
[11.26 12:56:17] svchost.exe (1216) - cdn-ima.33across.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cdn-ima.33across.com, IP=127.0.0.1, ttl=17709
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=live.primis.tech, IP=18.64.174.89, ttl=60
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=live.primis.tech, IP=18.64.174.128, ttl=60
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=live.primis.tech, IP=18.64.174.11, ttl=60
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=live.primis.tech, IP=18.64.174.35, ttl=60
[11.26 12:56:17] chrome.exe (7776) - live.primis.tech(18.64.174.89):443 (UDP) : direct connection
[11.26 12:56:17] chrome.exe (7776) - live.primis.tech(18.64.174.89):443 (UDP) : direct connection
[11.26 12:56:17] chrome.exe (7776) - cdn-ima.33across.com(127.0.0.1):443 matching Localhost rule : direct connection
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cdn.id5-sync.com, IP=104.20.23.13, ttl=161
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cdn.id5-sync.com, IP=172.66.169.55, ttl=161
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=secure.cdn.fastclick.net, IP=184.31.178.225, ttl=7
[11.26 12:56:17] chrome.exe (7776) - cdn.id5-sync.com(104.20.23.13):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:17] chrome.exe (7776) - secure.cdn.fastclick.net(184.31.178.225):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=aax.amazon-adsystem.com
[11.26 12:56:17] svchost.exe (1216) - aax.amazon-adsystem.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=aax.amazon-adsystem.com, IP=3.163.53.25, ttl=47
[11.26 12:56:17] chrome.exe (7776) - aax.amazon-adsystem.com(3.163.53.25):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:17] chrome.exe (7776) - config.aps.amazon-adsystem.com(143.204.23.47):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=pa.openx.net
[11.26 12:56:17] svchost.exe (1216) - pa.openx.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=s2s.t13.io
[11.26 12:56:17] svchost.exe (1216) - s2s.t13.io resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=ib.adnxs.com
[11.26 12:56:17] svchost.exe (1216) - ib.adnxs.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=fastlane.rubiconproject.com
[11.26 12:56:17] svchost.exe (1216) - fastlane.rubiconproject.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=ap.lijit.com
[11.26 12:56:17] svchost.exe (1216) - ap.lijit.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=rtb.openx.net
[11.26 12:56:17] svchost.exe (1216) - rtb.openx.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=htlb.casalemedia.com
[11.26 12:56:17] svchost.exe (1216) - htlb.casalemedia.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=grid-bidder.criteo.com
[11.26 12:56:17] svchost.exe (1216) - grid-bidder.criteo.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=pa.openx.net, IP=34.36.214.49, ttl=90
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=s2s.t13.io, IP=34.107.140.113, ttl=3596
[11.26 12:56:17] chrome.exe (7776) - pa.openx.net(34.36.214.49):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:17] chrome.exe (7776) - s2s.t13.io(34.107.140.113):443 (UDP) : direct connection
[11.26 12:56:17] chrome.exe (7776) - s2s.t13.io(34.107.140.113):443 (UDP) : direct connection
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=tlx.3lift.com
[11.26 12:56:17] svchost.exe (1216) - tlx.3lift.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=direct.adsrvr.org
[11.26 12:56:17] svchost.exe (1216) - direct.adsrvr.org resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=prebid.media.net
[11.26 12:56:17] svchost.exe (1216) - prebid.media.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=grid.bidswitch.net
[11.26 12:56:17] svchost.exe (1216) - grid.bidswitch.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=s.seedtag.com
[11.26 12:56:17] svchost.exe (1216) - s.seedtag.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=ads.yieldmo.com
[11.26 12:56:17] svchost.exe (1216) - ads.yieldmo.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=c.pub.network
[11.26 12:56:17] svchost.exe (1216) - c.pub.network resolve via 192.168.101.1:53 : DNS
[11.26 12:56:17] chrome.exe (7776) - cdn-ima.33across.com(127.0.0.1):443 matching Localhost rule : direct connection
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ib.adnxs.com, IP=68.67.181.231, ttl=28
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ib.adnxs.com, IP=68.67.160.186, ttl=28
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ib.adnxs.com, IP=68.67.160.184, ttl=28
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ib.adnxs.com, IP=68.67.160.114, ttl=28
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ib.adnxs.com, IP=68.67.161.182, ttl=28
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ib.adnxs.com, IP=68.67.179.153, ttl=28
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ib.adnxs.com, IP=68.67.160.76, ttl=28
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ib.adnxs.com, IP=68.67.179.89, ttl=28
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ib.adnxs.com, IP=68.67.181.102, ttl=28
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ib.adnxs.com, IP=68.67.179.87, ttl=28
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ib.adnxs.com, IP=68.67.161.208, ttl=28
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ib.adnxs.com, IP=68.67.160.117, ttl=28
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=fastlane.rubiconproject.com, IP=69.173.146.10, ttl=135
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ap.lijit.com, IP=3.225.53.188, ttl=37
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ap.lijit.com, IP=34.232.30.205, ttl=37
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ap.lijit.com, IP=52.3.143.68, ttl=37
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ap.lijit.com, IP=52.6.245.31, ttl=37
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ap.lijit.com, IP=98.85.150.29, ttl=37
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ap.lijit.com, IP=18.209.142.170, ttl=37
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ap.lijit.com, IP=34.205.0.146, ttl=37
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ap.lijit.com, IP=54.145.125.235, ttl=37
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=rtb.openx.net, IP=35.186.253.211, ttl=20
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=rtb.openx.net, IP=35.227.252.103, ttl=20
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=htlb.casalemedia.com, IP=104.18.27.193, ttl=74
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=htlb.casalemedia.com, IP=104.18.26.193, ttl=74
[11.26 12:56:17] chrome.exe (7776) - ap.lijit.com(3.225.53.188):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:17] chrome.exe (7776) - htlb.casalemedia.com(104.18.27.193):443 (UDP) : direct connection
[11.26 12:56:17] chrome.exe (7776) - htlb.casalemedia.com(104.18.27.193):443 (UDP) : direct connection
[11.26 12:56:17] chrome.exe (7776) - fastlane.rubiconproject.com(69.173.146.10):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:17] chrome.exe (7776) - ib.adnxs.com(68.67.181.231):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:17] chrome.exe (7776) - rtb.openx.net(35.186.253.211):443 (UDP) : direct connection
[11.26 12:56:17] chrome.exe (7776) - rtb.openx.net(35.186.253.211):443 (UDP) : direct connection
[11.26 12:56:17] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=hbopenbid.pubmatic.com
[11.26 12:56:17] svchost.exe (1216) - hbopenbid.pubmatic.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=grid-bidder.criteo.com, IP=74.119.117.12, ttl=2183
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=tlx.3lift.com, IP=3.208.175.5, ttl=25
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=tlx.3lift.com, IP=3.233.167.98, ttl=25
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=tlx.3lift.com, IP=54.158.18.149, ttl=25
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=tlx.3lift.com, IP=3.226.121.246, ttl=25
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=tlx.3lift.com, IP=34.192.42.219, ttl=25
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=prebid.media.net, IP=34.36.209.34, ttl=58
[11.26 12:56:18] chrome.exe (7776) - cdn.id5-sync.com(104.20.23.13):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - secure.cdn.fastclick.net(184.31.178.225):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - prebid.media.net(34.36.209.34):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - prebid.media.net(34.36.209.34):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - grid-bidder.criteo.com(74.119.117.12):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - tlx.3lift.com(3.208.175.5):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=s.seedtag.com, IP=34.149.50.64, ttl=197
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ads.yieldmo.com, IP=100.21.132.215, ttl=298
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ads.yieldmo.com, IP=50.112.85.63, ttl=298
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ads.yieldmo.com, IP=35.80.155.161, ttl=298
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ads.yieldmo.com, IP=52.34.193.153, ttl=298
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ads.yieldmo.com, IP=54.201.162.35, ttl=298
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ads.yieldmo.com, IP=52.89.29.154, ttl=298
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ads.yieldmo.com, IP=44.232.151.184, ttl=298
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ads.yieldmo.com, IP=44.242.18.131, ttl=298
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ads.yieldmo.com, IP=52.34.135.47, ttl=298
[11.26 12:56:18] chrome.exe (7776) - s.seedtag.com(34.149.50.64):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - s.seedtag.com(34.149.50.64):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - ads.yieldmo.com(100.21.132.215):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - s2s.t13.io(34.107.140.113):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - rtb.openx.net(35.186.253.211):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=hbopenbid.pubmatic.com, IP=207.65.37.179, ttl=141
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=grid.bidswitch.net, IP=74.119.117.5, ttl=3169
[11.26 12:56:18] chrome.exe (7776) - hbopenbid.pubmatic.com(207.65.37.179):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - grid.bidswitch.net(74.119.117.5):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - prebid.media.net(34.36.209.34):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=direct.adsrvr.org, IP=199.250.161.129, ttl=300
[11.26 12:56:18] chrome.exe (7776) - s.seedtag.com(34.149.50.64):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - direct.adsrvr.org(199.250.161.129):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - cmp.inmobi.com(18.155.252.127):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=c.pub.network, IP=34.160.152.31, ttl=300
[11.26 12:56:18] chrome.exe (7776) - c.pub.network(34.160.152.31):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - c.pub.network(34.160.152.31):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - aax.amazon-adsystem.com(3.163.53.25):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - c.pub.network(34.160.152.31):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - pa.openx.net(34.36.214.49):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - ap.lijit.com(3.225.53.188):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - fastlane.rubiconproject.com(69.173.146.10):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - ib.adnxs.com(68.67.181.231):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - grid-bidder.criteo.com(74.119.117.12):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - tlx.3lift.com(3.208.175.5):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - ads.yieldmo.com(100.21.132.215):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - hbopenbid.pubmatic.com(207.65.37.179):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - grid.bidswitch.net(74.119.117.5):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - c.pub.network(34.160.152.31):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - c.pub.network(34.160.152.31):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - direct.adsrvr.org(199.250.161.129):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - cmp.inmobi.com(18.155.252.127):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - c.pub.network(34.160.152.31):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=u.openx.net
[11.26 12:56:18] svchost.exe (1216) - u.openx.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=cs-server-s2s.yellowblue.io
[11.26 12:56:18] svchost.exe (1216) - cs-server-s2s.yellowblue.io resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=gum.criteo.com
[11.26 12:56:18] svchost.exe (1216) - gum.criteo.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=api.rlcdn.com
[11.26 12:56:18] svchost.exe (1216) - api.rlcdn.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=id5-sync.com
[11.26 12:56:18] svchost.exe (1216) - id5-sync.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=pl.primis.tech
[11.26 12:56:18] svchost.exe (1216) - pl.primis.tech resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=pixel.quantserve.com
[11.26 12:56:18] svchost.exe (1216) - pixel.quantserve.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=x.bidswitch.net
[11.26 12:56:18] svchost.exe (1216) - x.bidswitch.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=match.adsrvr.org
[11.26 12:56:18] svchost.exe (1216) - match.adsrvr.org resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=csync.loopme.me
[11.26 12:56:18] svchost.exe (1216) - csync.loopme.me resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=eb2.3lift.com
[11.26 12:56:18] svchost.exe (1216) - eb2.3lift.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=pixel.rubiconproject.com
[11.26 12:56:18] svchost.exe (1216) - pixel.rubiconproject.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=ssum-sec.casalemedia.com
[11.26 12:56:18] svchost.exe (1216) - ssum-sec.casalemedia.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=ups.analytics.yahoo.com
[11.26 12:56:18] svchost.exe (1216) - ups.analytics.yahoo.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=cs.media.net
[11.26 12:56:18] svchost.exe (1216) - cs.media.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=ssbsync-global.smartadserver.com
[11.26 12:56:18] svchost.exe (1216) - ssbsync-global.smartadserver.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=mb9eo.publishers.tremorhub.com
[11.26 12:56:18] svchost.exe (1216) - mb9eo.publishers.tremorhub.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=cm.adform.net
[11.26 12:56:18] svchost.exe (1216) - cm.adform.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=sync.1rx.io
[11.26 12:56:18] svchost.exe (1216) - sync.1rx.io resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=match.sharethrough.com
[11.26 12:56:18] svchost.exe (1216) - match.sharethrough.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=sync.kueezrtb.com
[11.26 12:56:18] svchost.exe (1216) - sync.kueezrtb.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=sync.ingage.tech
[11.26 12:56:18] svchost.exe (1216) - sync.ingage.tech resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=prebid.a-mo.net
[11.26 12:56:18] svchost.exe (1216) - prebid.a-mo.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=sync.ottadvisors.com
[11.26 12:56:18] svchost.exe (1216) - sync.ottadvisors.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=sync.inmobi.com
[11.26 12:56:18] svchost.exe (1216) - sync.inmobi.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=user-sync.fwmrm.net
[11.26 12:56:18] svchost.exe (1216) - user-sync.fwmrm.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=pubads.g.doubleclick.net
[11.26 12:56:18] svchost.exe (1216) - pubads.g.doubleclick.net resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=pagead2.googlesyndication.com
[11.26 12:56:18] svchost.exe (1216) - pagead2.googlesyndication.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=u.openx.net, IP=35.244.159.8, ttl=236
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=u.openx.net, IP=34.98.64.218, ttl=236
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cs-server-s2s.yellowblue.io, IP=34.4.35.11, ttl=144
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=gum.criteo.com, IP=74.119.117.62, ttl=1427
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=id5-sync.com, IP=162.19.138.82, ttl=163
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=id5-sync.com, IP=141.95.98.64, ttl=163
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=id5-sync.com, IP=162.19.138.119, ttl=163
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=id5-sync.com, IP=162.19.138.116, ttl=163
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=id5-sync.com, IP=162.19.138.118, ttl=163
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=id5-sync.com, IP=162.19.138.120, ttl=163
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=id5-sync.com, IP=162.19.138.83, ttl=163
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=id5-sync.com, IP=141.95.98.65, ttl=163
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=id5-sync.com, IP=141.95.33.120, ttl=163
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=id5-sync.com, IP=162.19.138.117, ttl=163
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=id5-sync.com, IP=57.129.85.132, ttl=163
[11.26 12:56:18] chrome.exe (7776) - u.openx.net(35.244.159.8):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - cs-server-s2s.yellowblue.io(34.4.35.11):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - u.openx.net(35.244.159.8):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - id5-sync.com(162.19.138.82):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - gum.criteo.com(74.119.117.62):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - ib.adnxs.com(68.67.181.231):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=sync.ingage.tech, IP=104.18.27.216, ttl=59
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=sync.ingage.tech, IP=104.18.26.216, ttl=59
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=sync.ottadvisors.com, IP=8.2.109.242, ttl=515
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=pubads.g.doubleclick.net, IP=172.217.30.162, ttl=237
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=pagead2.googlesyndication.com, IP=172.217.28.98, ttl=126
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=x.bidswitch.net, IP=35.211.202.130, ttl=81
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=match.adsrvr.org, IP=3.33.220.150, ttl=2327
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=match.adsrvr.org, IP=35.71.131.137, ttl=2327
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=match.adsrvr.org, IP=52.223.40.198, ttl=2327
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=match.adsrvr.org, IP=15.197.193.217, ttl=2327
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=csync.loopme.me, IP=35.214.190.220, ttl=2624
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=csync.loopme.me, IP=34.1.234.235, ttl=2624
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=csync.loopme.me, IP=34.3.93.119, ttl=2624
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=csync.loopme.me, IP=35.214.236.30, ttl=2624
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=csync.loopme.me, IP=35.214.245.4, ttl=2624
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=csync.loopme.me, IP=35.214.200.229, ttl=2624
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=csync.loopme.me, IP=35.214.161.212, ttl=2624
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=csync.loopme.me, IP=35.214.135.16, ttl=2624
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=eb2.3lift.com, IP=35.71.139.29, ttl=50
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=eb2.3lift.com, IP=52.223.22.214, ttl=50
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssum-sec.casalemedia.com, IP=104.18.26.193, ttl=115
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssum-sec.casalemedia.com, IP=104.18.27.193, ttl=115
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ups.analytics.yahoo.com, IP=69.147.92.12, ttl=58
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ups.analytics.yahoo.com, IP=69.147.92.11, ttl=58
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cs.media.net, IP=35.227.244.76, ttl=10
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=mb9eo.publishers.tremorhub.com, IP=23.21.44.231, ttl=30
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=mb9eo.publishers.tremorhub.com, IP=44.198.140.76, ttl=30
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=mb9eo.publishers.tremorhub.com, IP=100.26.138.138, ttl=30
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=mb9eo.publishers.tremorhub.com, IP=52.73.161.151, ttl=30
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=mb9eo.publishers.tremorhub.com, IP=3.230.121.227, ttl=30
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=mb9eo.publishers.tremorhub.com, IP=18.232.221.189, ttl=30
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=mb9eo.publishers.tremorhub.com, IP=3.218.158.65, ttl=30
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=mb9eo.publishers.tremorhub.com, IP=52.21.101.39, ttl=30
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=sync.1rx.io, IP=69.194.240.13, ttl=76
[11.26 12:56:18] chrome.exe (7776) - pubads.g.doubleclick.net(172.217.30.162):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - x.bidswitch.net(35.211.202.130):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - cs.media.net(35.227.244.76):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - pubads.g.doubleclick.net(172.217.30.162):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - sync.ottadvisors.com(8.2.109.242):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - sync.ingage.tech(104.18.27.216):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - cs.media.net(35.227.244.76):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - sync.1rx.io(69.194.240.13):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - ups.analytics.yahoo.com(69.147.92.12):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - eb2.3lift.com(35.71.139.29):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - mb9eo.publishers.tremorhub.com(23.21.44.231):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - match.adsrvr.org(3.33.220.150):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - csync.loopme.me(35.214.190.220):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=pixel.quantserve.com, IP=192.184.68.215, ttl=845
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=pixel.quantserve.com, IP=192.184.68.254, ttl=845
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=pixel.quantserve.com, IP=192.184.68.166, ttl=845
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=pixel.rubiconproject.com, IP=216.19.192.2, ttl=66
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=pl.primis.tech, IP=18.64.174.128, ttl=60
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=pl.primis.tech, IP=18.64.174.89, ttl=60
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=pl.primis.tech, IP=18.64.174.35, ttl=60
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=pl.primis.tech, IP=18.64.174.11, ttl=60
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=api.rlcdn.com, IP=34.107.165.188, ttl=60
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=match.sharethrough.com, IP=54.172.66.51, ttl=119
[11.26 12:56:18] chrome.exe (7776) - pixel.rubiconproject.com(216.19.192.2):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - match.sharethrough.com(54.172.66.51):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - pixel.quantserve.com(192.184.68.215):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - api.rlcdn.com(34.107.165.188):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - u.openx.net(35.244.159.8):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=prebid.a-mo.net, IP=131.153.13.102, ttl=14
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=prebid.a-mo.net, IP=131.153.13.101, ttl=14
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=prebid.a-mo.net, IP=131.153.13.103, ttl=14
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=prebid.a-mo.net, IP=131.153.13.100, ttl=14
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=sync.kueezrtb.com, IP=159.203.186.209, ttl=239
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=sync.kueezrtb.com, IP=159.89.230.187, ttl=239
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=23.105.12.143, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=216.22.16.37, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=216.22.16.53, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=23.105.14.100, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=216.22.16.36, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=23.105.12.170, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=23.105.14.101, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=216.22.16.68, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=23.105.12.117, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=216.22.16.52, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=216.22.16.4, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=216.22.16.5, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=23.105.12.116, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=23.105.12.171, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=23.105.12.159, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=216.22.16.69, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=23.105.12.158, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=ssbsync-global.smartadserver.com, IP=23.105.12.142, ttl=151
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cm.adform.net, IP=37.157.5.49, ttl=30
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=cm.adform.net, IP=37.157.5.86, ttl=30
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=user-sync.fwmrm.net, IP=3.145.229.109, ttl=9
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=user-sync.fwmrm.net, IP=3.231.143.19, ttl=9
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=user-sync.fwmrm.net, IP=3.145.229.130, ttl=9
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=user-sync.fwmrm.net, IP=3.231.143.27, ttl=9
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=user-sync.fwmrm.net, IP=3.231.143.14, ttl=9
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=user-sync.fwmrm.net, IP=3.231.143.36, ttl=9
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=user-sync.fwmrm.net, IP=3.144.50.132, ttl=9
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=user-sync.fwmrm.net, IP=3.144.50.142, ttl=9
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=user-sync.fwmrm.net, IP=3.231.143.24, ttl=9
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=user-sync.fwmrm.net, IP=3.144.50.133, ttl=9
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=sync.inmobi.com, IP=35.212.59.62, ttl=353
[11.26 12:56:18] chrome.exe (7776) - prebid.a-mo.net(131.153.13.102):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - sync.kueezrtb.com(159.203.186.209):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - ssbsync-global.smartadserver.com(23.105.12.143):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - sync.inmobi.com(35.212.59.62):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - user-sync.fwmrm.net(3.145.229.109):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - cm.adform.net(37.157.5.49):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - cmp.inmobi.com(18.155.252.127):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:18] chrome.exe (7776) - cs.media.net(35.227.244.76):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=prod.us-east-1.cxm-bcn.publisher-services.amazon.dev
[11.26 12:56:18] svchost.exe (1216) - prod.us-east-1.cxm-bcn.publisher-services.amazon.dev resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=tpc.googlesyndication.com
[11.26 12:56:18] svchost.exe (1216) - tpc.googlesyndication.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=prod.us-east-1.cxm-bcn.publisher-services.amazon.dev, IP=34.193.40.254, ttl=19
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=prod.us-east-1.cxm-bcn.publisher-services.amazon.dev, IP=34.230.169.17, ttl=19
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=prod.us-east-1.cxm-bcn.publisher-services.amazon.dev, IP=54.84.79.105, ttl=19
[11.26 12:56:18] chrome.exe (7776) - prod.us-east-1.cxm-bcn.publisher-services.amazon.dev(34.193.40.254):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - pubads.g.doubleclick.net(172.217.30.162):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - pubads.g.doubleclick.net(172.217.30.162):443 (UDP) : direct connection
[11.26 12:56:18] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=tpc.googlesyndication.com, IP=142.251.132.1, ttl=85
[11.26 12:56:18] chrome.exe (7776) - tpc.googlesyndication.com(142.251.132.1):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - tpc.googlesyndication.com(142.251.132.1):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - x.bidswitch.net(35.211.202.130):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - cs-server-s2s.yellowblue.io(34.4.35.11):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - id5-sync.com(162.19.138.82):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - gum.criteo.com(74.119.117.62):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - ib.adnxs.com(68.67.181.231):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - ap.lijit.com(3.225.53.188):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - ads.yieldmo.com(100.21.132.215):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - sync.ottadvisors.com(8.2.109.242):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - sync.ingage.tech(104.18.27.216):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - sync.1rx.io(69.194.240.13):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - ups.analytics.yahoo.com(69.147.92.12):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - eb2.3lift.com(35.71.139.29):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - mb9eo.publishers.tremorhub.com(23.21.44.231):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - match.adsrvr.org(3.33.220.150):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - csync.loopme.me(35.214.190.220):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - gum.criteo.com(74.119.117.62):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - pixel.rubiconproject.com(216.19.192.2):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - match.sharethrough.com(54.172.66.51):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - pixel.quantserve.com(192.184.68.215):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - api.rlcdn.com(34.107.165.188):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - tpc.googlesyndication.com(142.251.132.1):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - tpc.googlesyndication.com(142.251.132.1):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - prebid.a-mo.net(131.153.13.102):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - sync.kueezrtb.com(159.203.186.209):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - ssbsync-global.smartadserver.com(23.105.12.143):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - sync.inmobi.com(35.212.59.62):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - user-sync.fwmrm.net(3.145.229.109):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - cm.adform.net(37.157.5.49):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - pagead2.googlesyndication.com(172.217.28.98):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - pagead2.googlesyndication.com(172.217.28.98):443 (UDP) : direct connection
[11.26 12:56:18] chrome.exe (7776) - prod.us-east-1.cxm-bcn.publisher-services.amazon.dev(34.193.40.254):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:18] chrome.exe (7776) - aax.amazon-adsystem.com(3.163.53.25):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:19] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=prebid-server.rubiconproject.com
[11.26 12:56:19] svchost.exe (1216) - prebid-server.rubiconproject.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:19] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP request: AF=2, Type=1, Name=clients4.google.com
[11.26 12:56:19] svchost.exe (1216) - clients4.google.com resolve via 192.168.101.1:53 : DNS
[11.26 12:56:19] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=prebid-server.rubiconproject.com, IP=216.19.192.6, ttl=144
[11.26 12:56:19] svchost.exe (1216) - 192.168.101.1:53 DNS-UDP response: AF=2, Name=clients4.google.com, IP=172.217.30.206, ttl=86
[11.26 12:56:19] chrome.exe (7776) - clients4.google.com(172.217.30.206):443 (UDP) : direct connection
[11.26 12:56:19] chrome.exe (7776) - clients4.google.com(172.217.30.206):443 (UDP) : direct connection
[11.26 12:56:19] chrome.exe (7776) - optimise.net(34.111.152.239):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:19] chrome.exe (7776) - www.clarity.ms(4.153.187.221):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:20] chrome.exe (7776) - www.clarity.ms(4.153.187.221):443 close, 1756 bytes (1.71 KB) sent, 0 bytes received, lifetime <1 sec
[11.26 12:56:20] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:20] chrome.exe (7776) - www.clarity.ms(4.153.187.221):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:22] chrome.exe (7776) - config.aps.amazon-adsystem.com(143.204.23.47):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:22] chrome.exe (7776) - cdn.id5-sync.com(104.20.23.13):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:22] chrome.exe (7776) - s2s.t13.io(34.107.140.113):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:22] chrome.exe (7776) - ib.adnxs.com(68.67.181.231):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:22] chrome.exe (7776) - secure.cdn.fastclick.net(184.31.178.225):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:22] chrome.exe (7776) - rtb.openx.net(35.186.253.211):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:22] chrome.exe (7776) - prebid.media.net(34.36.209.34):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:22] chrome.exe (7776) - pa.openx.net(34.36.214.49):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:22] chrome.exe (7776) - pixel.quantserve.com(192.184.68.215):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:22] chrome.exe (7776) - cdn.id5-sync.com(104.20.23.13):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:22] chrome.exe (7776) - pa.openx.net(34.36.214.49):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:22] chrome.exe (7776) - direct.adsrvr.org(199.250.161.129):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - ups.analytics.yahoo.com(69.147.92.12):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - sync.1rx.io(69.194.240.13):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - c.pub.network(34.160.152.31):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - s.seedtag.com(34.149.50.64):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - fastlane.rubiconproject.com(69.173.146.10):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - prebid.a-mo.net(131.153.13.102):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - sync.kueezrtb.com(159.203.186.209):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - static.adsafeprotected.com(3.166.181.107):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - tlx.3lift.com(3.208.175.5):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - ap.lijit.com(3.225.53.188):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - sync.ingage.tech(104.18.27.216):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - eb2.3lift.com(35.71.139.29):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - hbopenbid.pubmatic.com(207.65.37.179):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - aax.amazon-adsystem.com(3.163.53.25):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - mb9eo.publishers.tremorhub.com(23.21.44.231):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - ap.lijit.com(3.225.53.188):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - gum.criteo.com(74.119.117.62):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - user-sync.fwmrm.net(3.145.229.109):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - prod.us-east-1.cxm-bcn.publisher-services.amazon.dev(34.193.40.254):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - csync.loopme.me(35.214.190.220):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - ib.adnxs.com(68.67.181.231):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - user-sync.fwmrm.net(3.145.229.109):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - x.bidswitch.net(35.211.202.130):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - ads.yieldmo.com(100.21.132.215):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - sync.ingage.tech(104.18.27.216):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - grid-bidder.criteo.com(74.119.117.12):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - c.pub.network(34.160.152.31):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:23] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:23] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 (UDP) : direct connection
[11.26 12:56:23] chrome.exe (7776) - sentry-api.tripleten.com(172.66.40.120):443 (UDP) : direct connection
[11.26 12:56:23] chrome.exe (7776) - grid-bidder.criteo.com(74.119.117.12):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:24] chrome.exe (7776) - ap.lijit.com(3.225.53.188):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:24] chrome.exe (7776) - ib.adnxs.com(68.67.181.231):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:24] chrome.exe (7776) - ups.analytics.yahoo.com(69.147.92.12):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:24] chrome.exe (7776) - gum.criteo.com(74.119.117.62):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:24] chrome.exe (7776) - aax.amazon-adsystem.com(3.163.53.25):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:24] chrome.exe (7776) - sync.inmobi.com(35.212.59.62):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:24] chrome.exe (7776) - config.aps.amazon-adsystem.com(143.204.23.47):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:24] chrome.exe (7776) - gum.criteo.com(74.119.117.62):443 close, 1724 bytes (1.68 KB) sent, 0 bytes received, lifetime <1 sec
[11.26 12:56:25] chrome.exe (7776) - aax.amazon-adsystem.com(3.163.53.25):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:25] chrome.exe (7776) - prod.us-east-1.cxm-bcn.publisher-services.amazon.dev(34.193.40.254):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:25] chrome.exe (7776) - ssbsync-global.smartadserver.com(23.105.12.143):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:25] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:26] chrome.exe (7776) - a.nel.cloudflare.com(35.190.80.1):443 (UDP) : direct connection
[11.26 12:56:26] chrome.exe (7776) - a.nel.cloudflare.com(35.190.80.1):443 (UDP) : direct connection
[11.26 12:56:26] chrome.exe (7776) - csync.loopme.me(35.214.190.220):443 close, 1821 bytes (1.77 KB) sent, 3522 bytes (3.43 KB) received, lifetime <1 sec
[11.26 12:56:26] chrome.exe (7776) - a.nel.cloudflare.com(35.190.80.1):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:26] chrome.exe (7776) - match.sharethrough.com(54.172.66.51):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:26] chrome.exe (7776) - cmp.inmobi.com(18.155.252.127):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:26] chrome.exe (7776) - cm.adform.net(37.157.5.49):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:26] chrome.exe (7776) - sync.ottadvisors.com(8.2.109.242):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:26] chrome.exe (7776) - direct.adsrvr.org(199.250.161.129):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:26] chrome.exe (7776) - pixel.rubiconproject.com(216.19.192.2):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:26] chrome.exe (7776) - sync.inmobi.com(35.212.59.62):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:26] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:26] chrome.exe (7776) - sentry-api.tripleten.com(172.66.43.136):443 (UDP) : direct connection
[11.26 12:56:26] chrome.exe (7776) - sentry-api.tripleten.com(172.66.43.136):443 (UDP) : direct connection
[11.26 12:56:26] chrome.exe (7776) - ads.yieldmo.com(100.21.132.215):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:26] chrome.exe (7776) - gum.criteo.com(74.119.117.62):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:27] chrome.exe (7776) - csync.loopme.me(35.214.190.220):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:27] chrome.exe (7776) - www.clarity.ms(4.153.187.221):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:27] chrome.exe (7776) - grid.bidswitch.net(74.119.117.5):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:27] chrome.exe (7776) - pixel.quantserve.com(192.184.68.215):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:27] chrome.exe (7776) - sync.ottadvisors.com(8.2.109.242):443 close, 1762 bytes (1.72 KB) sent, 0 bytes received, lifetime <1 sec
[11.26 12:56:27] chrome.exe (7776) - sync.ottadvisors.com(8.2.109.242):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:27] chrome.exe (7776) - cm.adform.net(37.157.5.49):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:27] chrome.exe (7776) - match.adsrvr.org(3.33.220.150):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:28] chrome.exe (7776) - tlx.3lift.com(3.208.175.5):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:28] chrome.exe (7776) - ads.yieldmo.com(100.21.132.215):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:28] chrome.exe (7776) - www.clarity.ms(4.153.187.221):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:28] chrome.exe (7776) - stats.g.doubleclick.net(74.125.139.157):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:28] chrome.exe (7776) - match.sharethrough.com(54.172.66.51):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:28] chrome.exe (7776) - fastlane.rubiconproject.com(69.173.146.10):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:29] chrome.exe (7776) - stats.g.doubleclick.net(74.125.139.154):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:29] chrome.exe (7776) - match.sharethrough.com(54.172.66.51):443 close, 1732 bytes (1.69 KB) sent, 0 bytes received, lifetime <1 sec
[11.26 12:56:29] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:29] chrome.exe (7776) - match.sharethrough.com(54.172.66.51):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:30] chrome.exe (7776) - a.nel.cloudflare.com(35.190.80.1):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:31] chrome.exe (7776) - aax.amazon-adsystem.com(3.163.53.25):443 close, 1765 bytes (1.72 KB) sent, 2988 bytes (2.91 KB) received, lifetime <1 sec
[11.26 12:56:31] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:31] chrome.exe (7776) - x.bidswitch.net(35.211.202.130):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:31] chrome.exe (7776) - sync.ottadvisors.com(8.2.109.242):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:31] chrome.exe (7776) - api.rlcdn.com(34.107.165.188):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:31] chrome.exe (7776) - api.omappapi.com(104.18.3.9):443 close, 2726 bytes (2.66 KB) sent, 2559 bytes (2.49 KB) received, lifetime <1 sec
[11.26 12:56:32] chrome.exe (7776) - c.amazon-adsystem.com(3.174.237.92):443 close, 2676 bytes (2.61 KB) sent, 91706 bytes (89.5 KB) received, lifetime <1 sec
[11.26 12:56:33] chrome.exe (7776) - cmp.inmobi.com(18.155.252.127):443 close, 2811 bytes (2.74 KB) sent, 2420 bytes (2.36 KB) received, lifetime <1 sec
[11.26 12:56:33] chrome.exe (7776) - stats.g.doubleclick.net(74.125.139.157):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:33] chrome.exe (7776) - stats.g.doubleclick.net(74.125.139.154):443 close, 3002 bytes (2.93 KB) sent, 5939 bytes (5.79 KB) received, lifetime <1 sec
[11.26 12:56:33] chrome.exe (7776) - eb2.3lift.com(35.71.139.29):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:33] chrome.exe (7776) - prebid.a-mo.net(131.153.13.102):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:35] chrome.exe (7776) - gum.criteo.com(74.119.117.62):443 close, 3528 bytes (3.44 KB) sent, 1734 bytes (1.69 KB) received, lifetime <1 sec
[11.26 12:56:35] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:37] chrome.exe (7776) - secure.cdn.fastclick.net(184.31.178.225):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:37] chrome.exe (7776) - cs-server-s2s.yellowblue.io(34.4.35.11):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:37] chrome.exe (7776) - hbopenbid.pubmatic.com(207.65.37.179):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:37] chrome.exe (7776) - match.adsrvr.org(3.33.220.150):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:37] chrome.exe (7776) - match.adsrvr.org(35.71.131.137):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:37] chrome.exe (7776) - grid.bidswitch.net(74.119.117.5):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:37] chrome.exe (7776) - ib.adnxs.com(68.67.181.231):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:37] chrome.exe (7776) - ib.adnxs.com(68.67.160.186):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:37] chrome.exe (7776) - sync.kueezrtb.com(159.203.186.209):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:37] chrome.exe (7776) - sync.kueezrtb.com(159.89.230.187):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:37] chrome.exe (7776) - sync.1rx.io(69.194.240.13):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:38] chrome.exe (7776) - css-tricks.com(104.18.39.21):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:38] chrome.exe (7776) - api.rlcdn.com(34.107.165.188):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:38] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:39] chrome.exe (7776) - cmp.inmobi.com(18.155.252.111):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:39] chrome.exe (7776) - css-tricks.com(172.64.148.235):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:39] chrome.exe (7776) - id5-sync.com(141.95.98.64):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:39] chrome.exe (7776) - mb9eo.publishers.tremorhub.com(44.198.140.76):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:39] chrome.exe (7776) - u.openx.net(34.98.64.218):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:39] chrome.exe (7776) - id5-sync.com(162.19.138.82):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:39] chrome.exe (7776) - id5-sync.com(141.95.98.64):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:39] chrome.exe (7776) - ssbsync-global.smartadserver.com(216.22.16.37):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:40] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:40] chrome.exe (7776) - cs.media.net(35.227.244.76):443 error : A connection request was canceled before the completion.
[11.26 12:56:40] chrome.exe (7776) - u.openx.net(35.244.159.8):443 error : A connection request was canceled before the completion.
[11.26 12:56:40] chrome.exe (7776) - id5-sync.com(162.19.138.82):443 error : A connection request was canceled before the completion.
[11.26 12:56:40] chrome.exe (7776) - cmp.inmobi.com(18.155.252.127):443 error : A connection request was canceled before the completion.
[11.26 12:56:41] chrome.exe (7776) - ssbsync-global.smartadserver.com(23.105.12.143):443 error : A connection request was canceled before the completion.
[11.26 12:56:41] chrome.exe (7776) - prod.us-east-1.cxm-bcn.publisher-services.amazon.dev(34.193.40.254):443 close, 2554 bytes (2.49 KB) sent, 4921 bytes (4.80 KB) received, lifetime <1 sec
[11.26 12:56:41] chrome.exe (7776) - pixel.rubiconproject.com(216.19.192.2):443 error : A connection request was canceled before the completion.
[11.26 12:56:41] chrome.exe (7776) - mb9eo.publishers.tremorhub.com(23.21.44.231):443 error : A connection request was canceled before the completion.
[11.26 12:56:41] chrome.exe (7776) - aax.amazon-adsystem.com(3.163.53.25):443 close, 2450 bytes (2.39 KB) sent, 7445 bytes (7.27 KB) received, lifetime <1 sec
[11.26 12:56:41] chrome.exe (7776) - cs-server-s2s.yellowblue.io(34.4.35.11):443 error : Could not connect through proxy 34.124.190.108(34.124.190.108):8080 - Proxy closed the connection unexpectedly.
[11.26 12:56:41] chrome.exe (7776) - cm.adform.net(37.157.5.49):443 close, 1755 bytes (1.71 KB) sent, 0 bytes received, lifetime <1 sec
[11.26 12:56:41] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:41] chrome.exe (7776) - cm.adform.net(37.157.5.49):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:41] chrome.exe (7776) - direct.adsrvr.org(199.250.161.129):443 close, 1823 bytes (1.78 KB) sent, 0 bytes received, lifetime <1 sec
[11.26 12:56:41] chrome.exe (7776) - direct.adsrvr.org(199.250.161.129):443 matching Default rule : using proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:42] chrome.exe (7776) - sync.ottadvisors.com(8.2.109.242):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:43] chrome.exe (7776) - css-tricks.com(104.18.39.21):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:43] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connection
[11.26 12:56:43] chrome.exe (7776) - match.sharethrough.com(54.172.66.51):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:44] chrome.exe (7776) - cmp.inmobi.com(18.155.252.111):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:44] chrome.exe (7776) - id5-sync.com(141.95.98.64):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:44] chrome.exe (7776) - match.adsrvr.org(35.71.131.137):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:44] chrome.exe (7776) - ssbsync-global.smartadserver.com(216.22.16.37):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:44] chrome.exe (7776) - id5-sync.com(141.95.98.64):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:45] chrome.exe (7776) - ib.adnxs.com(68.67.160.186):443 open through proxy 34.124.190.108:8080 SOCKS5
[11.26 12:56:48] chrome.exe (7776) - [2001:4860:4860::8888]:443 (UDP) (IPv6) : direct connectionwhat can i do to fix this???? my chrome does not change my ip address
Last edited by a moderator:
