Portmap.io Reviews

1. Ihor

   about 6 years ago
   WORST SERVICE i ever see

   Did not worked at all. No VPN connections, NO ssh connections... Did not work at all. No option to connect. Not working in my country and "No refund" :(

   I got fooled with such fake service. NOT RECOMMENDING. use ngrok instead. Better for 800% that this

   🏁 Competitors: Simple Port Forwarding

   👎 Cons:    Design|Price|Pricing|Ssh|Not working|Fake

HTTP Reviews

Portmap.io mentions (34)

• How do hackers hide their ip in reverse shells?

  I once used portmap.io for reverse shell in ethical hacking classes. Source: about 3 years ago

• OpenVPNnot working and i dont know what to do

  So I use portmap.io for OpenVPN like I saw in tutorials but I found out it is not working because my ip didn't change when I looked up what my ip was. Source: about 3 years ago

• SSH into a personal computer in Jio Network using public IP

  I have a personal computer in the Jio Network at my home and I want to access it using ssh from another network. But in order to port forward my router I am stuck since Jio uses CGNAT if I am not mistaken and there is no use if I portforward. What other solutions do I have? I tried using portmap.io but I couldnt configure ssh in it (I dont want to use openVPN) so what other options do I have? Source: over 3 years ago

• port forwarding/tunneling

  I'm basically looking for a free version of https://portmap.io/ -- they will do this, but custom domains are $4/month. Source: almost 4 years ago

• port triggering to replace port forwarding

  I would recommend trying again with port forwarding, or some other solution like this: https://portmap.io/ which is a kind of reverse tunnel made for situations like yours. That site has a free tier which allows a single forward. Source: almost 4 years ago

HTTP mentions (9)

• The History of HTTP

  HTTP/1.1 was first published as RFC 2068 (The Proposed Standard) in January 1997. HTTP/1.1 protocol was refined over two revisions, RFC 2616 published in June 1999 and RFC 7230-RFC 7235 published in June 2014 before the release of HTTP/2. The HTTP/1.1 standard (RFC 2616) remained stable for over 15 years. In 2022, HTTP/1.1 was updated again with RFC 9110 & RFC 9112. - Source: dev.to / 9 months ago

• State management in Svelte apps

  HTTP was invented as a stateless protocol, which means that each request fully encapsulates all of the information necessary to return a correct response. So historically, web pages never had to worry about managing state - each request to a URL with parameters or with a form submission would receive a response with all of the HTML that the browser needed to render content. - Source: dev.to / about 2 years ago

• Evolving the Web: Discovering the History of HTTP Versions

  HTTP/1.1 was such a game changer for the Internet that it works so well that even through two revisions, RFC 2616 published in June 1999 and RFC 7230– RFC 7235 published in June 2014, HTTP/1.1 was extremely stable until the release of HTTP/2.0 in 2014 — Nearly 18 years later. Before continuing to the next section about HTTP/2.0, let us revisit what journey HTTP/1.1 has been through. - Source: dev.to / about 3 years ago

• Poll: Are client web requests sent to upstream servers or downstream servers?

  On the one hand, it just seems natural that "upstream" refers to the inbound request being sent from one system to another. It takes effort (connection pooling, throttling, retries, etc.) to make a request to an (upstream) dependency, just as it takes effort to swim upstream. The response is (usually) easy... Just return it... hence, "downstream". Recall the usual meaning of "upload" and "download". Upstream seems... - Source: Hacker News / over 4 years ago

• How to cache TCP, SSL handshake on ALB?

  To me it sounds like you’ve not solved this as the config you’ve mentioned is about preventing “illegal” (none RFC7230 ) requests, it isn’t really related to the problem you posted. Source: over 4 years ago