Detection of domain name system hijacking

1. A computer-implemented method for detecting a Domain Name Service (DNS) hijacking, the computer-implemented method comprising the steps of:

resolving domain names in a hijack target group list to Internet Protocol (IP) addresses;

resolving domain names in a control group list to IP addresses, wherein the domain names in the control group list are prevalent domain names;

determining, based on the resolving of domain names in the hijack target group list, whether two domain names in the hijack target group list resolved to a common IP address;

in response to determining that two domain names in the hijack target group list resolved to the common IP address, determining, based on the resolving of the domain names in the control group list, whether any domain name in the control group list resolved to the same IP address as any other domain name in either the hijack target group list or the control group list; and

in response to determining that no domain names in the control group list resolved to the same IP address as any other domain name in either the hijack target group list or the control group list, indicating a DNS hijacking has occurred.

2. The computer-implemented method of claim 1 , further comprising, in response to determining the two domain names in the hijack target group list resolved to the common IP address, determining if the two domain names resolving to the common IP address belong to a same subgroup.

3. The computer-implemented method of claim 1 , wherein the step of resolving the domain names in the hijack target group list further comprises:

sending a DNS request from a network security scanner coupled to a user computing device, wherein the DNS request includes DNS server setting values of the user computing device; and

in response to the DNS request, receiving records information.

4. The computer-implemented method of claim 3 , further comprising:

reporting the occurrence of the DNS hijacking to an application; and

resetting, by the application, the DNS server setting values of the user computing device.

5. The computer-implemented method of claim 1 , wherein the prevalent domain names in the control group list are domain names of at least one of non-profit internet services, universities, open-source projects, and consumer product vendors.

6. The computer-implemented method of claim 1 , further comprising reporting the occurrence of the DNS hijacking to a user.

7. The computer-implemented method of claim 1 , further comprising reporting the occurrence of the DNS hijacking to an application.

8. A computer-implemented method for detecting a malicious Domain Name Service (DNS) hijacking, the computer-implemented method comprising the steps of:

allowing a computing device to issue queries for Internet Protocol (IP) addresses associated with domain names, the computing device being coupled with a network security scanner having a first domain name group list and a second domain name group list, wherein domain names in the second domain name group list are prevalent domain names;

resolving the domain names in the first domain name group list;

resolving the domain names in the second domain name group list;

determining, based on the resolving of domain names in the first domain name group list, whether two domain names in the first domain name group list resolved to a common IP address;

in response to determining that two domain names in the first domain name group list resolved to the common IP address, determining whether any domain name in the second domain name group list resolved to the same IP address as any other domain name in either the first domain name group list or the second domain name group list, including determining if the two domain names resolved to the common IP address belong to a same subgroup; and

in response to determining that no domain names in the second domain name group list resolved to the same IP address as any other domain name in either the first domain name group list or the second domain name group list, indicating a DNS hijacking has occurred.

9. The computer-implemented method of claim 8 , further comprising the steps of:

checking the resolved domain names against a blacklist.

10. The computer-implemented method of claim 8 , wherein the prevalent domain names in the second domain name group list are domain names of at least one of non-profit internet services, universities, open-source projects, and consumer product vendors.

11. The computer-implemented method of claim 8 , further comprising reporting the occurrence of the DNS hijacking to a user.

12. The computer-implemented method of claim 8 , further comprising reporting the occurrence of the DNS hijacking to an application.

13. The computer-implemented method of claim 8 , further comprising:

sending a DNS request from the network security scanner, wherein the DNS request includes DNS server setting values of the computing device;

reporting the occurrence of the DNS hijacking to an application; and

resetting, by the application, the DNS server setting values of the computing device.

14. A non-transitory computer readable storage medium having a program stored thereon, the program causing the computer to execute the steps of:

resolving domain names in a first domain name group list to Internet Protocol (IP) addresses;

resolving domain names in a control group list to IP addresses, wherein the domain names in the control group list are prevalent domain names;

determining, based on the resolving of domain names in the first domain name group list, whether two domain names in the first domain name group list resolved to a common IP address;

in response to determining that two domain names in the first domain name group list resolved to the common IP address, determining, based on the resolving of the domain names in the control group list, whether any domain name in the control group list resolved to the same IP address as any other domain name in either the first domain name group list or the control group list; and

in response to determining that no domain names in the control group list resolved to the same IP address as any other domain name in either the first domain name group list or the control group list, indicating a Domain Name Service (DNS) hijacking has occurred.

15. The non-transitory computer readable storage medium of claim 14 , the program further causing the computer to, in response to determining the two domain names in the first domain name group list resolved to the common IP address, determining if the two domain names resolving to the common IP address belong to a same subgroup.

16. The non-transitory computer readable storage medium of claim 14 , wherein the prevalent domain names in the control group list are domain names of at least one of non-profit internet services, universities, open-source projects, and consumer product vendors.

17. The non-transitory computer readable storage medium of claim 14 , the program further causing the computer to report the occurrence of the DNS hijacking to a user.

18. The non-transitory computer readable storage medium of claim 14 , the program further causing the computer to report the occurrence of the DNS hijacking to an application.

19. The non-transitory computer readable storage medium of claim 14 , the program further causing the computer to:

send a DNS request from a network security scanner coupled to the computer, wherein the DNS request includes DNS server setting values of the computer;

report the occurrence of the DNS hijacking to an application; and

reset, by the application, the DNS server setting values of the computer.

20. The non-transitory computer readable storage medium of claim 14 , the program further causing the computer to check the resolved domain names against a blacklist.