• Content count

  • Joined

  • Last visited

  • Speed Test

    My Results


About mudmanc4

  • Rank
    TMN Seasoned Veteran
  • Birthday January 1

Contact Methods

  • AIM
  • MSN
  • Website URL
  • ICQ
  • Yahoo
  • Skype

Profile Information

  • Gender
  • Location
    In The Plex

Recent Profile Visitors

71,090 profile views
  1. A vulnerability was discovered in how CGI scripts are used by Red Hat products that leverage PHP, Go, Python, and other scripting languages. Several web servers, web frameworks and programming languages (most commonly in a CGI environment) will set the environmental variable “HTTP_PROXY” based on data from incoming requests (e.g. a request header called “Proxy” with user supplied data). The environmental variable “HTTP_PROXY” is used by numerous web client software packages to specify a remote proxy server to use for HTTP, and in some cases HTTPS requests. As a result when a web application runs it may be possible for an attacker to specify a proxy server which the application uses for subsequent outgoing requests, allowing a "Man-in-the-Middle" attack. This flaw has been given the name HTTPoxy . Background Information CGI and Environment variables The HTTP server uses a set of environment variables to pass information to the CGI script. Some of those environment variables are used to communicate certain aspects of the HTTP request, like the content type, the TCP port, the hostname, or request method (for example, GET or POST). There is a different set of environment variables, that the RFC calls "Protocol-Specific Meta-Variables", which are used to pass the values of HTTP headers to the CGI script. The mapping of HTTP headers to environment variables follows a standard procedure: the HTTP header name is converted to uppercase, "-" is replaced with "_", and "HTTP_" is prefixed. For example, the "Cookie" header is passed using the "HTTP_COOKIE" environment variable and the "Proxy" header is passed using the "HTTP_PROXY" environment variable. Please note that the "Proxy" header is not an official standard header, nor is it in the provisional header registry. The "Proxy" header should not be used by any standards compliant applications or clients. [...] Source
  2. Hey

    Straw Welcome to @milla
  3. Understood, I took it in the most literal sense.
  4. @FriskyMoose A site first must be blacklisted, which would mean no access what so ever. And this has nothing to do with throughput. has been around since 2001 Domain Name: TESTMY.NET Registrar: GODADDY.COM, LLC Sponsoring Registrar IANA ID: 146 Whois Server: Referral URL: Name Server: ERIN.NS.CLOUDFLARE.COM Name Server: KIP.NS.CLOUDFLARE.COM Status: clientDeleteProhibited Status: clientRenewProhibited Status: clientTransferProhibited Status: clientUpdateProhibited Updated Date: 02-apr-2016 Creation Date: 09-oct-2001 Expiration Date: 09-oct-2024 In fact that is how I found out about, through the ISP I had at the time , they as in (the head network engineer) recommended that I come over here and get a real world test result.
  5. I wonder if 'it' still busts a grumpy if the chunder box is not under the puckered brown eye. Or if the poor sap gets the bubble guts and starts doing the Tijuana trot across the counter top if it does not agree with what you feed it. Yup nothin' like a mechanical sphincter squeezing out a steamer, just for you.
  6. I see, my thoughts are maxmind is still working to geographical locations of IP blocks, between assigned, ownership, organization and final allocation. None the less, keep testing, check all the servers frequently, the data you acquire can then begin to focus in on where the issues are, and when. Nice connection by the way.
  7. So you have the cognitive skills to use a 'smart phone', and your faculties are active enough to purchase something like this, yet you still require a pill pewping robot, which if you notice, stares you down while pinching off a couple chunks of medical excrement for you to indulge in. Something is wrong, very very wrong
  8. @Bunnie Just a note, 'MyHosting' average speeds database is 88.2Mbps, so I would say you are doing rather well for a VPS host.
  9. @Bunnie There is more to this story isn't there. We can see from Singapore which is the geographical test point location, or origin. When the tests are taken to a Singapore server, the tests show very consistent results. When testing oversea, and not using a flash based test, here at shows functional yet depressed results. This is a great example of having a real world test to show peering and or network issues. Running a traceroute from the origin to the test server will show the points in which the bottleneck in, whether it be specific DPI QOS engineering, or network congestion.
  10. @Firfoxenator I would try using a different browser, it is possible there is an add on / plugin of some sort causing the issue. Also if there is a different machine you have access to?
  11. Outside of the fact on how many levels of just plain wrong Comodo [has been] in it's entirety is for it's actions. However so, I'd like to thank Comodo for bringing the attention to Lets Encrypt in order to assist in accelerating the broad usage we are now seeing. Encryption in the form of basic SSL certificates if at all possible, should be the standard by it's nature, free and open source, again by the nature of the direction. The Internet Security Research Group (ISRG) has thus far found the channels to bring this reality to the masses. Any attempt to thwart, obscure, or obtain in any fashion or copy write basic internet data transmission security, is an act of aggression against the nature of all that is good in the advancements of securing the means which we transmit data.
  12. We have confirmed that Comodo submitted Requests for Express Abandonment for all three trademark registration applications in question. We’re happy to see this positive step towards resolution, and will continue to monitor the requests as they make their way through the system. We’d like to thank our community for their support. Some months ago, it came to our attention that Comodo Group, Inc., is attempting to register at least three trademarks for the term “Let’s Encrypt,” for a variety of CA-related services [1][2][3]. These trademark applications were filed long after the Internet Security Research Group (ISRG) started using the name Let’s Encrypt publicly in November of 2014, and despite the fact Comodo’s “intent to use” trademark filings acknowledge that it has never used “Let’s Encrypt” as a brand. We’ve forged relationships with millions of websites and users under the name Let’s Encrypt, furthering our mission to make encryption free, easy, and accessible to everyone. We’ve also worked hard to build our unique identity within the community and to make that identity a reliable indicator of quality. We take it very seriously when we see the potential for our users to be confused, or worse, the potential for a third party to damage the trust our users have placed in us by intentionally creating such confusion. By attempting to register trademarks for our name, Comodo is actively attempting to do just that. Since March of 2016 we have repeatedly asked Comodo to abandon their “Let’s Encrypt” applications, directly and through our attorneys, but they have refused to do so. We are clearly the first and senior user of “Let’s Encrypt” in relation to Internet security, including SSL/TLS certificates – both in terms of length of use and in terms of the widespread public association of that brand with our organization. Source
  13. Google Fiber, the high-speed internet-access business owned by Alphabet, has bought Webpass for an undisclosed sum. The deal will help Google expand its service into dense, urban areas like apartment buildings with multiple units. Webpass, available in cities that are in the San Francisco Bay Area and four other cities, specializes in providing high-speed internet service in urban areas. In a blog post announcing the deal, Webpass president Charles Barr said that the acquisition is expected to close this summer, subject to the standard regulatory approvals. Google did not comment on the deal, but the company confirmed it in a tweet:
  14. @Shyanoda You can convert the results here If you meant in your results page that I'm not sure about.
  15. @Downfall Run several tests here at, run at least two tests to each test server, which the locations are spread evenly through continents, this will give us some information as to how your ISP is peering, which could explain the real world results you are getting , compared to what you are paying for.