www.hostdomainzone.com

Host MonsterHostMonster的服务器名称很有规律,都是host***.hostmonster.com。

因为今天帮人买的一个HostMonster虚拟主机的IP被封了,购买完在国内就没法访问,新买的虚拟主机被分配到host187.hostmonster.com服务器上。于是想看看HostMonster的服务器共享IP到底有多少被封了。

搞了个小程序跑了一下,从host10到host278(host1至host9以及host400以后的不存在,host279至host400估计暂时尚未启用),测试的结果如下:

一共269台服务器,有75台服务器的IP被封了,被封率差不多达到1/3,所以运气差一点的话,新买的HostMonster虚拟主机就被封了,没法在国内访问,实在是个麻烦的事情。还是买一独立IP,这样用着才比较放心。

下面的是被封服务器(共享IP)的列表:

host15.hostmonster.com[74.220.202.15] – connect failed
host16.hostmonster.com[74.220.202.16] – connect failed
host21.hostmonster.com[74.220.202.21] – connect failed
host22.hostmonster.com[74.220.202.22] – connect failed
host31.hostmonster.com[74.220.202.31] – connect failed
host42.hostmonster.com[74.220.202.42] – connect failed
host43.hostmonster.com[74.220.202.43] – connect failed
host47.hostmonster.com[74.220.202.47] – connect failed
host54.hostmonster.com[74.220.203.54] – connect failed
host61.hostmonster.com[74.220.207.61] – connect failed
host70.hostmonster.com[74.220.207.70] – connect failed
host73.hostmonster.com[74.220.207.73] – connect failed
host74.hostmonster.com[74.220.207.74] – connect failed
host76.hostmonster.com[74.220.207.76] – connect failed
host77.hostmonster.com[74.220.207.77] – connect failed
host84.hostmonster.com[74.220.207.84] – connect failed
host86.hostmonster.com[74.220.207.86] – connect failed
host90.hostmonster.com[74.220.207.90] – connect failed
host93.hostmonster.com[74.220.207.93] – connect failed
host95.hostmonster.com[74.220.207.95] – connect failed
host96.hostmonster.com[74.220.207.96] – connect failed
host101.hostmonster.com[74.220.207.101] – connect failed
host106.hostmonster.com[74.220.207.106] – connect failed
host108.hostmonster.com[74.220.207.108] – connect failed
host110.hostmonster.com[74.220.207.110] – connect failed
host111.hostmonster.com[74.220.207.111] – connect failed
host118.hostmonster.com[74.220.207.118] – connect failed
host119.hostmonster.com[74.220.207.119] – connect failed
host121.hostmonster.com[74.220.207.121] – connect failed
host122.hostmonster.com[74.220.207.122] – connect failed
host123.hostmonster.com[74.220.207.123] – connect failed
host125.hostmonster.com[74.220.207.125] – connect failed
host126.hostmonster.com[74.220.207.126] – connect failed
host127.hostmonster.com[74.220.207.127] – connect failed
host128.hostmonster.com[74.220.207.128] – connect failed
host132.hostmonster.com[74.220.207.132] – connect failed
host136.hostmonster.com[74.220.207.136] – connect failed
host137.hostmonster.com[74.220.207.137] – connect failed
host141.hostmonster.com[74.220.207.141] – connect failed
host143.hostmonster.com[74.220.207.143] – connect failed
host144.hostmonster.com[74.220.207.144] – connect failed
host147.hostmonster.com[74.220.207.147] – connect failed
host149.hostmonster.com[74.220.207.149] – connect failed
host150.hostmonster.com[74.220.207.150] – connect failed
host153.hostmonster.com[74.220.207.153] – connect failed
host159.hostmonster.com[74.220.207.159] – connect failed
host166.hostmonster.com[74.220.207.166] – connect failed
host167.hostmonster.com[74.220.207.167] – connect failed
host169.hostmonster.com[74.220.207.169] – connect failed
host170.hostmonster.com[74.220.207.170] – connect failed
host172.hostmonster.com[74.220.207.172] – connect failed
host173.hostmonster.com[74.220.207.173] – connect failed
host176.hostmonster.com[74.220.207.176] – connect failed
host182.hostmonster.com[74.220.207.182] – connect failed
host183.hostmonster.com[74.220.207.183] – connect failed
host186.hostmonster.com[74.220.207.186] – connect failed
host187.hostmonster.com[74.220.207.187] – connect failed
host189.hostmonster.com[74.220.207.189] – connect failed
host190.hostmonster.com[74.220.207.190] – connect failed
host192.hostmonster.com[74.220.207.192] – connect failed
host193.hostmonster.com[74.220.207.193] – connect failed
host196.hostmonster.com[74.220.207.196] – connect failed
host197.hostmonster.com[74.220.207.197] – connect failed
host198.hostmonster.com[74.220.207.198] – connect failed
host204.hostmonster.com[74.220.215.204] – connect failed
host213.hostmonster.com[74.220.215.213] – connect failed
host215.hostmonster.com[74.220.215.215] – connect failed
host222.hostmonster.com[74.220.215.222] – connect failed
host238.hostmonster.com[74.220.215.238] – connect failed
host240.hostmonster.com[74.220.215.240] – connect failed
host246.hostmonster.com[74.220.215.246] – connect failed
host247.hostmonster.com[74.220.215.247] – connect failed
host250.hostmonster.com[74.220.215.250] – connect failed
host260.hostmonster.com[74.220.215.60] – connect failed
host265.hostmonster.com[74.220.215.65] – connect failed
269 servers tested,
75 servers(shared IPs) are blocked!

You can skip to the end and leave a comment. Pinging is currently not allowed.

bluehost美国虚拟主机-$5.95/月-无限空间/无限流量/一个免费域名

9 Comments to “有多少HostMonster的共享IP被封?”

  1. ejianfei says:

    July 20th, 2008 at 11:13 pm

    很强大,上一阵子 我的lu也被封了,一直很闹心

  2. 三个公司 类似的虚拟主机方案--Matt Heaton一招走天下 says:

    July 24th, 2008 at 9:54 am

    […] 对于BlueHost、HostMonster和FastDomain来说,他们只需要专心做好一件事情,显然这件事情可以做得相当的出色,他们也确实做得的很好。在以前的日志有多少HostMonster的共享IP被封?中我们可以看到HostMonster达到了近270台服务器,规模和发展的速度可见一斑。 […]

  3. sanp says:

    July 6th, 2009 at 5:57 pm

    惨,我刚买的hostmonster也在这个列表里….

  4. Beishan says:

    July 6th, 2009 at 8:49 pm

    @sanp
    IP是多少啊?如果共享IP被封了就买个独立IP呗

  5. 天涯 says:

    March 8th, 2010 at 5:05 pm

    请问怎样购买独立IP呢?

  6. Beishan says:

    March 8th, 2010 at 5:45 pm

    帐号通过验证审核后就可以直接在主机管理后台购买独立IP。

    帐号验证可以参考日志 HostMonster 主机账户验证教程

  7. 邢台驾校 says:

    March 14th, 2010 at 12:04 am

    独立IP不会被封吗?是不是只是减少被封的可能啊,不会被别人连累吧

  8. 邢台驾校 says:

    March 14th, 2010 at 12:06 am

    我看网上都说共享IP可能被封,所以看了老卫的文章后买了个IX的,虽说速度稍微不如HM的但送2个独立IP,所说不是很清楚这个的好处,还是觉得有了安全点

  9. Beishan says:

    March 14th, 2010 at 12:29 am

    独立IP的话,如果自己网站没什么问题,基本上不会被封

Leave a comment

为了做关键词或者推广的评论,直接删除,请不要费力

eleven2 Hosting