The Razor's Edge wrote:
> VanguardLH wrote:
>
>> MarkMonitor is a domain registrar along with providing services for
>> anti-piracy, anti-fraud, and brand protection. Several large companies
>> have many of their domains registered through MarkMonitor (e.g., Google
>> with their
1e100.net domain). So you could be loading a home page or
>> using extensions that connect to a domain protected by MarkMonitor. For
>> example, when using TPLs (tracking protection lists) in IE, it has to
>> get the updated adblocking blacklists from somewhere. When the TPLs get
>> updated, new blacklists get uploaded.
>
> I visited their site to verify who they are and although I am not that
> concerned about an open 443 connection established because the amount of
> data in is minimal, I still want to know why?
Markmonitor is the nameserver for many domains. When you visit a domain
that requires using Markmonitor's DNS server (to get an IP address for
the target site), the lookup may go back to Markmonitor's name server.
DNS requests go out via port 53. As yet, I've not heard there is a
ratified protocol to encrypt DNS requests although I remember reading a
draft or proposal to secure DNS connections (eliminate sniffing or MITM
attack to change who responds to the client's DNS request). I haven't
checked into DNScrypt for awhile to know if anyone is using it yet
https://www.opendns.com/about/innovations/dnscrypt/). Notice I say
*encrypted* DNS, not secure DNS because "secure" rarely means encrypted
versus filtering.
Yet you mentioned port 443 which is the port for encrypted HTTP (HTTPS).
So that takes out the DNS request from your computer via port 53. Do
you have auto-update enabled in any application? They could be
connecting to an update server via HTTPS which uses MarkMonitor's
services.
When you use SysInternals' TCPview to show current connections (well,
current and those waiting to get killed), is the PID (process ID) of the
explorer.exe instance (probably has the lowest PID number) with the
marmonitor connection the one for your desktop or another instance of
explorer.exe?
If you load SysInternals' TCPview and then run "taskkill /im
explorer.exe /f" (which means your desktop disappears), do TCPview show
the connection went away? It should disappear if all instances of
explorer.exe got killed. In TCPview, what is the state of those
markmonitor connections? Are they in CLOSE_WAIT state? All those will
disappear if you configure TCPview to *not* show unconnected endpoints.
Those are old connections whose client-side resources remain defined for
awhile to reduce the overhead should a process reconnect to that same
endpoint.
http://blogs.technet.com/b/janelewis/archive/2010/03/09/explaining-close-wait.aspx
If the process that created the connection doesn't complete the close
process then Windows is going to keep that limbo state in place. You
have something that is connecting to MarkMonitor but the defunct old
connections still in CLOSE_WAIT status aren't going to point you at what
created the connection. You need to configure TCPview to *not* show the
connections with unconnected endpoints (the server disconnected but the
client has yet to complete the close) and then watch for want process
creates a new and LISTENING state for a connection to MarkMonitor.
I suspect that explorer.exe is listed as the owning process because it
inherited the connections left behind an application badly exited or
crashed. Configure TCPview to *not* show unconnected endpoints (it will
still show CLOSE_WAIT pending disconnects) and watch for what process
creates new connections to MarkMonitor (those in LISTENING or
ESTABLISHED state).
All the LISTENING, CLOSE_WAIT, ESTABLISHED connections can be a bit much
to wade through in TCPview. That tool has no filtering function; i.e.,
you cannot tell it to show connections in specific states or look for
connections with specific endpoints (to where the connection goes).
Nirsoft's CurrPorts (haven't used this much) has filtering but it seems
basic (you cannot pick in which the criteria is applied). Nmap (there
is a Windows version) might allow better filtering but I've not use it
yet (it's in my Software of Interest folder) so you'll have to find out
it if will let you filter on connects just for MarkMonitor.
SysInternals TCPview just doesn't give you enough control over the data
it presents.