Advanced Uses for Google’s Site: Operator

You probably know that Google’s site: operator lets you restrict results to a site or domain. Search for [site:cnn.com iran] to restrict the results for “Iran” to CNN’s site, search for [site:googlesystem.blogspot.com gmail tips] to find Gmail tips from this blog. You can also use the site: operator for top-level domains and search for [site:fr debussy] or [site:edu ai].

Google’s site: operator is a lot more powerful than that. You can leave out some components of the address and replace them with asterisks. For example, you can find results from addresses that match this pattern: maps.*.com. Unfortunately, Google doesn’t show all the results that match the pattern.


You can also find results that have URLs which start with “news.” like “news.cnet.com” or “news.discovery.com”. Just search for [site:news.*].

What if you want to search Amazon’s international sites? Instead of typing [site:amazon.com OR site:amazon.co.uk OR site:amazon.ca OR site:amazon.de OR site:amazon.fr], just search for [site:amazon.*].

Google’s site: operator also works for directories. For example, you can find last year’s posts about Gmail by searching for [site:googlesystem.blogspot.com/2012 gmail].

You can even enter URLs that include parameters and leave out the parameters. Here’s a way to search the Google Maps help center: [site:support.google.com/maps/bin/answer.py inurl:”hl=en” 3d]. I’ve used the inurl: operator to restrict the results to English pages, but it’s not necessary to do that.

How to restrict the results for [imap] to answers from Google’s help centers? Search for: [site:support.google.com/*/answer imap]. 继续阅读




第一种: 自己编一个谷歌浏览器扩展,屏蔽谷歌hk\com域名跳转,强制谷歌SSL连接


名称:Google SSL Privacy Real Link



作者:Strike Welkin







Google SSL Privacy Real Link.crx




第二种: 使用AdBlock去广告扩展的人,增加一条规则,变成多功能扩展,屏蔽香港域名跳转


























感谢原作者:Strike Welkin



App Key:xiaomi
App Secret:3MqAdNoRLHomm4AECoURl7gds1sUIjun

App Key:31641035
App Secret:6a7c98c1eef2109622d0a08199a35bef

App Key:202088835
App Secret:9567e3782151dcfd1a9bd2dd099d957f

App Key:2540340328
App Secret:886cfb4e61fad4e4e9ba9dee625284dd

App Key:1206405345
App Secret:fa6095e113cd28fde6e14c7b7145c5c5

App Key:1905839263
App Secret:36b51c6ebf2dd3e5361f80f6c4506267

App Key:783190658
App Secret:7f63ae9eb3c1438e9f8932748ca8a341

App Key:5786724301
App Secret:5Jao51NF1i5PDC91hhI3ID86ucoDtn4C

App Key:569452181
App Secret:bbd573c3052999adcd026cbf88ffbf8e

App Key:31024382
App Secret:25c3e6b5763653d1e5b280884b45c51f

App Key:2849184197
App Secret:7338acf99a00412983f255767c7643d0

App Key:2702428363
App Secret:82d9b7c386000b0de0711a20f146fa44

App Key:211160679
App Secret:63b64d531b98c2dbff2443816f274dd3

App Key:82966982
App Secret:72d4545a28a46a6f329c4f2b1e949e6a

App Key:2440435914
App Secret:70dc2ae26780817793c9c533092171dd

App Key:2190063733
App Secret:9222f119671ebf566b74220768014afd

App Key:3442868347
App Secret:07b27d2c098eda5eec681abdde832a51

App Key:android
App Secret:5l0WXnhiY4pJ794KIJ7Rw5F45VXg9sjo

App Key:blackberry
App Secret:ivij24vyWpP0zE0M03r56RL2u8nu0L66

App Key:sxtab
App Secret:6b2BhcdpiCdyZaIh4O3S1zHAUoC6Zpql

App Key:sxandroid
App Secret:tYQO8S1RndCGgI3qNbiCEjG3cVaeOvq7

App Key:htc
App Secret:ybQv5D6BC2bIOqYV2wCsIs0dX9vV0xIG

App Key:x10
App Secret:rPVsSGvnz8erJ7w8sIICKEE70wQMRswU

App Key:me511
App Secret:5AgbUpV7fL2APXOkI04QnRhlGUdUlwy0

App Key:lp
App Secret:5EmMeHqPOYsLSQ2zjrdXHoUhqtD4QYGx

App Key:meizu_m9
App Secret:WQnVIAWDBmR9XV86YNAO97P3Xgk21az9

App Key:s60
App Secret:AbLmkn77N8j72iyE2Aup5RoRN8C0M3E5

App Key:tianyi
App Secret:DX2eXTXpGhnTeSoMcJs2BCpXQQKyzehf

App Key:tcl
App Secret:gPvIKBER6kF2wAe6POQF9mTL1W9I9Y8C

App Key:zhongxing
App Secret:sc2GRZT16abrHaUps2cydiQKvWizy8IE

App Key:huawei
App Secret:QUoQoFbH7LVmuCBhEwMKzC65R1JZDX0t

App Key:k_touch
App Secret:7d125GronKUP1rcgkOb8rqVjh2Q44fdx

App Key:tyw700
App Secret:nj3PK1AvukNAwXihZZg9PN6H文明用语b5QQb

App Key:yulong
App Secret:9qCZ3L9riYQRz4FznnwUGrv2uPjqBGEm

App Key:coolpad
App Secret:SuQmVobcpJxaNZRThXR4xsytbHUMOdFB

App Key: 413108509
App Secret: 4ec8c0340b5f2c39672226aebe17e62e

App Key: 4110068027
App Secret: db9e09f5f7113d321ea2097a781ede01

App Key: 1963173494
App Secret: 607c9befde09c241f404700380aeb117

App Key: 2688653569
App Secret: 09d2b979960fb95e2163419b727873a0



How to enable IPv6 on Vista & Win7

Windows Vista and Windows 7 both come equipped with dual stack IPv4/IPv6, and it can be enabled on Windows XP/SP2. On a default installation of Vista/Win7, IPv6 should already be operational. In order to fully test your IPv6 readiness, you will also need the services of a Tunnel Broker. A Tunnel Broker is a server that sits on both an IPv6 network and an IPv4 network. IPv6 packets are encapsulated inside an IPv4 packet and sent out over the IPv4 network. The server strips the IPv4 info and sends the packet on to the IPv6 server. Return packets follow the reverse route.

Vista/Win7 come equipped with the Teredo Tunnel, but it is not functional by default. To get all these working, the following services must be running:
IP Helper – Automatic Started
Windows Firewall – Automatic Started
Base Filtering Engine – Manual Started
Don’t ask me why the Firewall has to run, but Microsoft says that the Teredo Tunnel is a security risk. To the best of my knowledge, the Teredo Tunnel is the only one that will work behind a NAT router that does not support IPv6. It uses a technique similar to PPP networks, with a specific UDP port being used to maintain contact.

One of the major differences with IPv6 is that there can be multiple IP addresses. Since there is no longer a Netmask to determine if an address is on the local network, or if it has to be routed through a gateway, they have introduced something called a link-local address. If you go to the command prompt and enter the “ipconfig /all” command, you should see an address beginning with “fe80::” and ending with “%x” under the Local Area Connection. The “%x” is a random ID number assigned to the interface, and will be necessary to use at times (more on that later).

If the system only has a link-local and a Teredo tunnel IP address, the DNS will not return an IPv6 address. To overcome this limitation, we have to fool the system by adding another IPv6 address. If you are fortunate enough to have a router that supports IPv6 DHCP, one will already have been assigned to you. If not, you must manually enter it. Go to the Properties of your LAN or WiFi interface, and change it to have a static IPv6 address. The easiest solution is to use the converted IPv4 address with a netmask of 48. For example, a static IPv4 address of “” converts to “2002:c0a8:102::” (192 = c0h, 168 = a8h, 1 = 01h, 2 = 02h). Don’t configure a default gateway for this address, because there isn’t one. You will also need to configure IPv6 DNS servers. You can use any that you might have access to. Both OpenDNS and Google offer free public servers:
OpenDNS: 2620:0:ccc::2 & 2620:0:ccd::2
Google: 2001:4860:4860::8888 & 2001:4860:4860::8844
I personally use one of each.

Windows will now resolve IPv6 domain names. The simplest way to test this is to ping your own computer name (find under System in the Control Panel), or another computer name on your local network that supports IPv6. It should resolve the link-local address and complete the ping. For example:
C:\>ping donna2-pc
Pinging Donna2-PC [fe80::8d22:1710:b68c:37d9%9] from fe80::a5bb:d4f:e017:e25c%9 with 32 bytes of data:
Reply from fe80::8d22:1710:b68c:37d9%9: time<1ms
Reply from fe80::8d22:1710:b68c:37d9%9: time<1ms
Reply from fe80::8d22:1710:b68c:37d9%9: time<1ms
Reply from fe80::8d22:1710:b68c:37d9%9: time<1ms
Ping statistics for fe80::8d22:1710:b68c:37d9%9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
On one machine I had difficulty getting the ping command to use the correct interface. It wanted to use the Teredo link-local address instead of the ethernet adapter link-local address. I solved the problem by disabling the other Microsoft interface via the registry. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents
This key probably won’t exist and must be added as a REG_DWORD. The value is a bit map:
· Bit 0 Set to 1 to disable all IPv6 tunnel interfaces, including ISATAP, 6to4, and Teredo tunnels.
· Bit 1 Set to 1 to disable all 6to4-based interfaces.
· Bit 2 Set to 1 to disable all ISATAP-based interfaces.
· Bit 3 Set to 1 to disable all Teredo-based interfaces.
· Bit 4 Set to 1 to disable IPv6 over all non-tunnel interfaces, including LAN interfaces and *Point-to-Point Protocol (PPP)-based interfaces.
· Bit 5 Set to 1 to modify the default prefix policy table to prefer IPv4 to IPv6 when attempting connections.
To disable the ISATAP interface, I changed the value to 4 (bit 2).

At this point, we need to expose you to a command that has always been there, but wasn’t really used much with IPv4.
C:\>netsh int ipv6 show teredo
Teredo Parameters
Type : client
Server Name : teredo.ipv6.microsoft.com.
Client Refresh Interval : 30 seconds
Client Port : unspecified
State : dormant
Client Type : teredo host-specific relay
Network : managed
NAT : none (global connectivity)
“Int” is short for “interface”. If the state shows as “offline”, you may have to force Teredo into accepting your NAT router. This is done using the following command:
C:\>netsh int ipv6 set teredo type=enterpriseclient
If Teredo is now functional, then you should be able to find the interface index using the “ipconfig /all” command:
Tunnel adapter Local Area Connection* 6:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:142b:a209:30f9:a279(Preferred)
Link-local IPv6 Address . . . . . : fe80::142b:a209:30f9:a279%8(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
In the example above, the interface index is %8 for the Teredo interface. We need this number for the next command, since there is no default route to allow traffic to flow to the Internet.
C:\>netsh int ipv6 add route ::/0 interface=8
With this last step you should now be able to access IPv6 sites such as:
C:\>ping ipv6.google.com
Pinging ipv6.l.google.com [2001:4860:b006::69] from 2001:0:4137:9e76:249b:92d7:b464:60e9 with 32 bytes of data:
Reply from 2001:4860:b006::69: time=31ms
Reply from 2001:4860:b006::69: time=31ms
Reply from 2001:4860:b006::69: time=31ms
Reply from 2001:4860:b006::69: time=31ms
Ping statistics for 2001:4860:b006::69:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 31ms, Average = 31ms
It may take more than one attempt to activate the interface. Then try entering http://ipv6.google.com into your browser, and it should bring up Google’s IPv6 page.

Be aware that at this point in time, Windows will always prefer IPv4 over IPv6 if both exist for a given domain. We can change that behaviour by modifying the prefixpolicies table:
C:\>netsh int ipv6 show pre
Querying active state…
Precedence Label Prefix
———- —– ——————————–
50 0 ::1/128
40 1 ::/0
30 2 2002::/16
20 3 ::/96
10 4 ::ffff:0:0/96
5 5 2001::/32
But I will leave that for you to investigate on your own.