DNSSEC www.dnssec-tools.org with 8.8.8.8

[Anonymous]

Well I can't make heads or tails of this Community layout in where the boards are so here goes.

So I've got a 4G Dongle this it mostly a backup connection to my ISP virgin media I've been trying to work out a problem with dnssec and the test at www.dnssec-tools.org and think its down to your HTTP proxy so to test I use just 8.8.8.8 which supports dnssec set on the NIC so it must use that for DNS over 4G. Now when a test on virgin media with 8.8.8.8 for www.dnssec-tools.org it passes but on O2 4G it fails. At this point you might be thinking dnssec is not supported over 4G with O2? Wrong because it does at another dnssec site at dnssec.vs.uni-due.de and both pass.

So I'm very sure its down to the HTTP proxy you put on the O2 4G connection thats messing the DNS SEC test up for www.dnssec-tools.org

Anyone else seeing this?

thanks

[Martin-O2]

Hey @Anonymous did you have any luck getting to the bottom of this?

[MI5]

---

@Martin-O2 wrote:

Hey @Anonymous did you have any luck getting to the bottom of this?

---

Nicely worded 

[Anonymous]

Thiers sod all I can do about if your router this o2 4G Dongle connects to over 4G as in not my end your router doing 4G end that screws up the HTTP source code of the site when I receive it.

[Beenherebefore]

---

@MI5 wrote:

---

@Martin-O2 wrote:

Hey @Anonymous did you have any luck getting to the bottom of this?

---

Nicely worded 

---

Knowing what we know  ....I was tempted to comment but thought better of it........then you come along 

[MI5]

Subtle enough?

[Beenherebefore]

As expected......up to your usual standard !

[MI5]

That's OK then

[Beenherebefore]

At some point  we  you may have to explain 

[MI5]

Keep 'em guessing

[Anonymous]

Even Netalyzr shows:

And no I do not have a proxy set in my browser the proxy is the O2 router at the 4G not this is end.

tracetcp www.dnssec-tools.org

Tracing route to 192.94.214.6 [www.dnssec-tools.org] on port 80

Over a maximum of 30 hops.

1 3 ms 3 ms 3 ms 192.168.255.203

2 2 ms 2 ms 2 ms 192.168.3.1

3 * * * Request timed out.

4 117 ms 53 ms 153 ms 172.16.212.1

5 92 ms 151 ms 88 ms 172.16.212.10

6 130 ms 112 ms 49 ms 192.168.31.136

7 97 ms 123 ms 52 ms 172.25.40.1

8 Destination Reached in 123 ms. Connection established to 192.94.214.6

Trace Complete.

Content-based HTTP proxy detection (?): Warning
–

Changes to headers or contents sent between the client and our HTTP server show the presence of an otherwise unadvertised HTTP proxy.

The following headers had their capitalization modified by the proxy:

Content-Type: text/html
Last-Modified: Mon
01 Aug 2016 16:09:25 GMT
Set-Cookie: netAlizEd=BaR; path=/; domain=netalyzr.icsi.berkeley.edu
Content-Length: 466

The following headers were added by the proxy to HTTP responses:

Vary: User-Agent
Content-Encoding: gz­ip
Proxy-Connection: Ke­ep-Alive
Expires: Mon, 01 Aug­ 2016 16:14:19 GMT

The detected proxy reordered the headers sent from the server.

The detected HTTP proxy changed images that were sent from our server.

The detected HTTP proxy changed either the headers the client sent or the HTTP response from the server. We have captured the changes for further analysis.

Filetype-based filtering (?): Note
–
Files of type exe are modified by the network.
This appears due to a proxy which is performing compression, as a Content-Encoding: gzip header was added.


Sensitive proxy-introduced HTTP headers (?): 3 HTTP headers found
–

Our analysis indicates that an HTTP proxy injects headers into your web traffic that you should know about:

x-gateway = wap.london.02.net
Identifies the network GSM gateway and/or its location.
x-forwarded-for = 10.68.9.35
Reports your local IP address.
o2gw-id = 0A
Identifies uniquely the GSM gateway of the device.