MyHostingSrv has recently submitted their first ever offer to share with the LowEndBox community! We thought the offers looked like a great deal for SSD VPS’s, so here they are. They are offering three different specials to choose from, and their servers are located in Chicago, IL.
You can find their ToS/Legal Docs here. They accept PayPal, Credit Cards, Debit Cards, Bitcoin, Litecoin, Ethereum, Alipay and Amazon Pay as payment methods for you to choose from.
Here’s what they had to say:
“MyHostingSrv was founded with the purpose to offer the best hosting services to our customers. We have been facilitating thousands of clients, now hosting 30,000 domains across our entire network. Our servers are capable to offer 99.99% uptime to your website with high performance and fast responding equipment.
We offer different hosting packages with different rates which you can choose from as per you need. Please feel free to contact us if you need something different, MyHostingSrv will facilitate you with all of those services that you’ve ever expected from a hosting company!”
Here’s the offers:
3GB VPS (SSD)
| 4GB VPS (SSD)
| 8GB VPS (SSD)
|
Chicago, IL, USA
Test IPv4: 66.225.198.198
Test File: 1000MB
Host Node Specifications:
– Intel Xeon E3 Series Processors
– 32GB to 64GB of RAM
– 4x 1TB SSD’s
– Hardware RAID-10 (LSI)
– 1Gbps Uplink
Please let us know if you have any questions/comments and enjoy!
Related Posts:
- SteadyVPS – Dedicated Server offer for $35 a month out of Los Angeles datacenter - April 25, 2020
- WindowsVPS.Host – VPS plans starting at $5.50! - March 13, 2020
- HostNOC – Dedicated VPN offer for $4.99 a month! Secure, Safe and Private! - March 9, 2020
Hi , Can you(VPS-Provider) please INCLUDE these with any of your above VPS (virtual-private-server) service-instance offers (for the same price) ? and i have few extra questions:
(1) can you please add one IPv6 /64-subnet resource for the VPS ? a /64 IPv6-subnet has 18-QuinTillion-IPv6-addresses, a Server should have a minimum /64 IPv6 subnet recommended by IANA/IETF . do you have native IPv6-address pool or tunneled IPv6-address ? i & my partners need internet routable & native /64 IPv6-SUBNET for our business-project server apps that will run in a VPS . if you cannot provide 18QT-IPv6-Addresses ( a /64 IPv6-SUBNET ) , then can you provide atleast a smaller amount: 4-Billion-IPv6-Addresses ( 4BN = 4Bilions-IPv6 addresses are equivalent of one /96 IPv6-SUBNET ) ? If you can provide 18QT or 4BN IPv6-addresses then Can you also please setup your DNS-NameServer to point those address-range toward the NameServer(NS) that will be running inside the VPS ? and can you also add 1 more line of CNAME dns record that will point toward your own IPv6-range’s rDNS itself . ( if you agree i will give you those 2 lines of codes, so that you can further adjust/suite them ) . My server-apps inside the VPS will need to setup(add/delete / modify/query) PTR/rDNS dns-record for any of those provided IPv6-addresses very-quickly + instantly at any random moment for our new users . Manually setting-up each IPv6-address’s PTR/rDNS one by one for our project’s each new user is not going to work for our project functionalities, it will not be convenient when later we will have more users & need more automation.
(2) currently do you support setup of PTR/RDNS for IPv4 & IPv6 address thru your VPS control/management PANEL or via support-ticket ? does your panel have API support to setup PTR/RDNS instantly from the VPS’s server-apps ?
(3) do you respect+follow+uphold People+client+customer & their-user’s PRIVACY-RIGHTS ? and Do you follow Data Privacy+Protection+Security LAWS ? ( GDPR Laws . Laws similar to California SB-1386 civil code §§ 1798.29, 1798.82, 1798.84. CalOPPA code §§ 22575-22579. CCPA (AB-375 / SB-1121) code §§ 1798.100. etc. USA-Federal PRIVACY-LAWS have substantial “opt-out” requirements. etc )
(4) do you (or does your USP=upstream-service-provider) AUTO-SEND any (root/vnc/ssh / control-panel/web-portal / support-ticket-commuication) PASSWORD into any customer’s/client’s (or into any of your staff/admin’s) email-address thru OPEN EMAIL when any client/customer orders VPS or Reinstall-OS or changes PASSWORD, etc ? if you do then you’re violating various laws , please fix your bugs+policies . Do you allow clients/customers to setup the VPS root-password in the ( HTTPS based secure ) VPS-order webpage ? if you do then you are following at-least one good security+protection policy+law . Do you share any (Private/Personal) data/code from VPS with anyone else or with any 3rd-party ? if you do-not-share & if you guard/protect data/code, only then you are upholding People’s+User’s+Client’s+Customer’s Privacy-RIGHTS and following Privacy + Protection + Security, etc Laws.
(5) Full Root Access available for VPS ? TUN/TAP/PPP ? Virtualizor access ? Debian v9.9 or higher available ? VNC/SSH access ?
if you respond then thanks.
EXTRA-NOTES:
* When any EMAIL’s content is NOT-Encrypted With GPG/PGP/SMIME (keys/certs) Then that EMAIL is OPEN EMAIL.
* Data passing thru HTTP or FTP is OPEN.
* Data passing thru HTTPS is secure/ENCRYPTED . HTTPS is Encrypted with CA validated certificates/keys.
* Data passing thru SSH is secure/ENCRYPTED . SSH is Encrypted with PKI keys.
* Data passing thru FTPS, SFTP, etc are secure+encrypted . When you have option to use both, prefer FTPS (as it uses FTP over/thru SSH).
* Correct FCrDNS, PTR/RDNS, WHITELISTED-IP, SPF, etc are necessary for MAIL-server to send-out EMAILs into an “INBOX”, or else EMAILs are either REJECTED or placed into SPAM/TRASH folder.
* DNS is OPEN . DNS queries & answers can be secured by using DoH (DNS over/thru HTTPS) or DNS-over-TLS,etc . DNS answer’s authenticity can be verified by using DNSSEC.
* Certificate’s authenticity can be verified by CA root certs and also by using DNSSEC . Server’s SSH public Key(s),etc can be verified by DNSSEC.
* VPS (virtual-private-server) , is a SERVICE-instance, & provided /64 IPv6-net is a resource, etc, and all of those remains with you (VPS-Provider) , inside your own DataCenters/Servers . A remote Client/Customer/User with access to that VIRTUAL-server in your premise , cannot take the provided service/resource away from you & move into another VPS/location . So adding the 2 lines (NS & CNAME dns-records) in your DNS NameServer are NOT A REAL DELEGATION or SUB-DELEGATION , you did not really transfer control of your service+resource to another person/entity who can or able-to move-away from you with your resources, into another location . Adding those 2-lines of DNS codes are just a temporary attachment of a service+resource for the sake of providing service for a VPS(virtual-server) which remains with you in your own DataCenters/Servers . But we named it “DELEGATE” for the convenience of identifying this functionality , but in reality no real TRANSFER occurred , no real DELEGATION . You are merely providing/adding / attaching few service(s)+resource(s) in your VIRTUAL-server SERVICE-instance inside your own DataCenters/Servers, for a remote Client/Customer/User.