Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Phoenix

Region: Arizona

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


NetRange:       20.0.0.0 - 20.31.255.255
CIDR:           20.0.0.0/11
NetName:        MSFT
NetHandle:      NET-20-0-0-0-1
Parent:         NET20 (NET-20-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Microsoft Corporation (MSFT)
RegDate:        2017-10-18
Updated:        2021-12-14
Ref:            https://rdap.arin.net/registry/ip/20.0.0.0



OrgName:        Microsoft Corporation
OrgId:          MSFT
Address:        One Microsoft Way
City:           Redmond
StateProv:      WA
PostalCode:     98052
Country:        US
RegDate:        1998-07-10
Updated:        2025-06-10
Comment:        To report suspected security issues specific to traffic emanating from Microsoft online services, including the distribution of malicious content or other illicit or illegal material through a Microsoft online service, please submit reports to:
Comment:        * https://cert.microsoft.com.  
Comment:        
Comment:        For SPAM and other abuse issues, such as Microsoft Accounts, please contact:
Comment:        * abuse@microsoft.com.  
Comment:        
Comment:        To report security vulnerabilities in Microsoft products and services, please contact:
Comment:        * secure@microsoft.com.  
Comment:        
Comment:        For legal and law enforcement-related requests, please contact:
Comment:        * msndcc@microsoft.com
Comment:        
Comment:        For routing, peering or DNS issues, please 
Comment:        contact:
Comment:        * IOC@microsoft.com
Ref:            https://rdap.arin.net/registry/entity/MSFT


OrgTechHandle: BEDAR6-ARIN
OrgTechName:   Bedard, Dawn 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  dabedard@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/BEDAR6-ARIN

OrgTechHandle: MRPD-ARIN
OrgTechName:   Microsoft Routing, Peering, and DNS
OrgTechPhone:  +1-425-882-8080 
OrgTechEmail:  IOC@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/MRPD-ARIN

OrgAbuseHandle: MAC74-ARIN
OrgAbuseName:   Microsoft Abuse Contact
OrgAbusePhone:  +1-425-882-8080 
OrgAbuseEmail:  abuse@microsoft.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/MAC74-ARIN

OrgTechHandle: SINGH683-ARIN
OrgTechName:   Singh, Prachi 
OrgTechPhone:  +1-425-707-5601 
OrgTechEmail:  pracsin@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/SINGH683-ARIN

OrgTechHandle: IPHOS5-ARIN
OrgTechName:   IPHostmaster, IPHostmaster 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  iphostmaster@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/IPHOS5-ARIN

OrgRoutingHandle: CHATU3-ARIN
OrgRoutingName:   Chaturmohta, Somesh 
OrgRoutingPhone:  +1-425-882-8080 
OrgRoutingEmail:  someshch@microsoft.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/CHATU3-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 20.14.76.20
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35491
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.14.76.20.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026091501 1800 900 604800 86400

;; Query time: 5 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Sep 16 07:00:30 CST 2026
;; MSG SIZE  rcvd: 104
Host info
20.76.14.20.in-addr.arpa domain name pointer azpdws69fxg1.stretchoid.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
20.76.14.20.in-addr.arpa	name = azpdws69fxg1.stretchoid.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
49.88.112.115 attackspam
Oct 27 00:34:42 web1 sshd\[23144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.115  user=root
Oct 27 00:34:44 web1 sshd\[23144\]: Failed password for root from 49.88.112.115 port 13483 ssh2
Oct 27 00:36:59 web1 sshd\[23349\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.115  user=root
Oct 27 00:37:01 web1 sshd\[23349\]: Failed password for root from 49.88.112.115 port 14408 ssh2
Oct 27 00:41:00 web1 sshd\[23699\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.115  user=root
2019-10-27 18:45:20
45.136.111.109 attackspam
Oct 27 08:45:52   TCP Attack: SRC=45.136.111.109 DST=[Masked] LEN=40 TOS=0x08 PREC=0x20 TTL=240  PROTO=TCP SPT=54490 DPT=3011 WINDOW=1024 RES=0x00 SYN URGP=0
2019-10-27 18:59:19
195.223.59.201 attack
$f2bV_matches
2019-10-27 18:40:49
157.55.39.90 attack
157.55.39.90 - - - [27/Oct/2019:03:46:55 +0000] "GET /blog/page/8/ HTTP/1.1" 404 162 "-" "Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)" "-" "-"
2019-10-27 18:34:38
85.93.20.170 attackbotsspam
Connection by 85.93.20.170 on port: 45682 got caught by honeypot at 10/26/2019 11:33:51 PM
2019-10-27 18:42:18
77.247.108.77 attackbotsspam
firewall-block, port(s): 5038/tcp
2019-10-27 18:47:23
114.220.176.106 attack
Oct 27 05:35:59 herz-der-gamer sshd[4900]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.220.176.106  user=root
Oct 27 05:36:01 herz-der-gamer sshd[4900]: Failed password for root from 114.220.176.106 port 55405 ssh2
Oct 27 05:50:14 herz-der-gamer sshd[5174]: Invalid user magic from 114.220.176.106 port 54958
...
2019-10-27 19:01:22
79.188.68.90 attackspam
$f2bV_matches
2019-10-27 18:32:22
14.136.118.138 attackbots
2019-10-27T06:18:48.085658abusebot-5.cloudsearch.cf sshd\[29272\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=014136118138.ctinets.com  user=root
2019-10-27 18:37:12
185.76.34.87 attackspambots
2019-10-26T18:43:15.800290ldap.arvenenaske.de sshd[972]: Connection from 185.76.34.87 port 57840 on 5.199.128.55 port 22
2019-10-26T18:43:16.402466ldap.arvenenaske.de sshd[972]: Invalid user ftp03 from 185.76.34.87 port 57840
2019-10-26T18:43:16.475995ldap.arvenenaske.de sshd[972]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.76.34.87 user=ftp03
2019-10-26T18:43:16.480420ldap.arvenenaske.de sshd[972]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.76.34.87
2019-10-26T18:43:15.800290ldap.arvenenaske.de sshd[972]: Connection from 185.76.34.87 port 57840 on 5.199.128.55 port 22
2019-10-26T18:43:16.402466ldap.arvenenaske.de sshd[972]: Invalid user ftp03 from 185.76.34.87 port 57840
2019-10-26T18:43:18.232328ldap.arvenenaske.de sshd[972]: Failed password for invalid user ftp03 from 185.76.34.87 port 57840 ssh2
2019-10-26T18:50:23.112706ldap.arvenenaske.de sshd[984]: Connection from 185.........
------------------------------
2019-10-27 18:36:51
106.13.65.18 attack
Oct 26 19:45:45 hanapaa sshd\[20244\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.65.18  user=root
Oct 26 19:45:47 hanapaa sshd\[20244\]: Failed password for root from 106.13.65.18 port 52584 ssh2
Oct 26 19:51:10 hanapaa sshd\[20684\]: Invalid user user from 106.13.65.18
Oct 26 19:51:10 hanapaa sshd\[20684\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.65.18
Oct 26 19:51:12 hanapaa sshd\[20684\]: Failed password for invalid user user from 106.13.65.18 port 59348 ssh2
2019-10-27 18:47:47
133.130.113.128 attackbots
$f2bV_matches
2019-10-27 18:41:58
222.186.173.154 attackspam
Oct 27 13:34:07 server sshd\[11914\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.154  user=root
Oct 27 13:34:10 server sshd\[11914\]: Failed password for root from 222.186.173.154 port 57942 ssh2
Oct 27 13:34:14 server sshd\[11914\]: Failed password for root from 222.186.173.154 port 57942 ssh2
Oct 27 13:34:18 server sshd\[11914\]: Failed password for root from 222.186.173.154 port 57942 ssh2
Oct 27 13:34:23 server sshd\[11914\]: Failed password for root from 222.186.173.154 port 57942 ssh2
...
2019-10-27 18:36:16
104.236.75.186 attackbots
Automatic report - XMLRPC Attack
2019-10-27 18:58:48
77.222.60.203 attack
Oct 26 01:54:12 host sshd[14639]: reveeclipse mapping checking getaddrinfo for hostnameauunbaincowebe.myihor.ru [77.222.60.203] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 26 01:54:12 host sshd[14639]: Invalid user aw from 77.222.60.203
Oct 26 01:54:12 host sshd[14639]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.222.60.203 
Oct 26 01:54:14 host sshd[14639]: Failed password for invalid user aw from 77.222.60.203 port 41084 ssh2
Oct 26 01:54:14 host sshd[14639]: Received disconnect from 77.222.60.203: 11: Bye Bye [preauth]
Oct 26 01:59:06 host sshd[29797]: reveeclipse mapping checking getaddrinfo for hostnameauunbaincowebe.myihor.ru [77.222.60.203] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 26 01:59:06 host sshd[29797]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.222.60.203  user=r.r
Oct 26 01:59:08 host sshd[29797]: Failed password for r.r from 77.222.60.203 port 58596 ssh2


........
---------------------------------------
2019-10-27 18:29:25

Recently Reported IPs

172.110.223.84 103.77.192.132 112.13.112.182 45.135.194.24
118.193.58.125 54.243.13.14 52.91.228.25 3.95.176.169
34.84.176.198 33.121.139.96 32.119.246.198 31.1.113.1
2606:4700:10::6814:7472 30.92.55.16 3.33.151.178 32.83.250.115
52.180.152.222 207.154.254.156 64.226.91.58 164.92.247.156