必须是合法有效的IP地址, 可以是IPv4或者是IPv6, 例如127.0.0.1或者2001:DB8:0:0:8:800:200C:417A
基本信息:

城市(city): San Antonio

省份(region): Texas

国家(country): United States

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
#
# 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:       40.74.0.0 - 40.125.127.255
CIDR:           40.120.0.0/14, 40.124.0.0/16, 40.74.0.0/15, 40.96.0.0/12, 40.80.0.0/12, 40.112.0.0/13, 40.125.0.0/17, 40.76.0.0/14
NetName:        MSFT
NetHandle:      NET-40-74-0-0-1
Parent:         NET40 (NET-40-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Microsoft Corporation (MSFT)
RegDate:        2015-02-23
Updated:        2021-12-14
Ref:            https://rdap.arin.net/registry/ip/40.74.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

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

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


#
# 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信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 40.124.116.160
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63012
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;40.124.116.160.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 12 10:30:40 CST 2026
;; MSG SIZE  rcvd: 107
HOST信息:
160.116.124.40.in-addr.arpa domain name pointer azpdsg0681w3.stretchoid.com.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
160.116.124.40.in-addr.arpa	name = azpdsg0681w3.stretchoid.com.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
49.88.112.112 attack
Nov 28 11:55:07 webhost01 sshd[29442]: Failed password for root from 49.88.112.112 port 43251 ssh2
...
2019-11-28 13:08:08
190.46.157.140 attackspam
Nov 28 06:53:55 server sshd\[7257\]: Invalid user supra from 190.46.157.140 port 50737
Nov 28 06:53:55 server sshd\[7257\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.46.157.140
Nov 28 06:53:57 server sshd\[7257\]: Failed password for invalid user supra from 190.46.157.140 port 50737 ssh2
Nov 28 06:58:13 server sshd\[24242\]: Invalid user ssh from 190.46.157.140 port 39919
Nov 28 06:58:13 server sshd\[24242\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.46.157.140
2019-11-28 13:23:08
223.11.158.211 attack
3389BruteforceFW23
2019-11-28 13:33:57
113.21.117.250 attackspambots
Email IMAP login failure
2019-11-28 13:24:37
134.175.111.215 attack
Nov 28 07:32:19 server sshd\[17700\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.111.215  user=root
Nov 28 07:32:21 server sshd\[17700\]: Failed password for root from 134.175.111.215 port 36712 ssh2
Nov 28 07:59:51 server sshd\[24634\]: Invalid user awesome from 134.175.111.215
Nov 28 07:59:51 server sshd\[24634\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.111.215 
Nov 28 07:59:53 server sshd\[24634\]: Failed password for invalid user awesome from 134.175.111.215 port 35778 ssh2
...
2019-11-28 13:20:40
118.24.151.43 attackspambots
Nov 28 06:15:14 localhost sshd\[24629\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.151.43  user=root
Nov 28 06:15:16 localhost sshd\[24629\]: Failed password for root from 118.24.151.43 port 57374 ssh2
Nov 28 06:19:46 localhost sshd\[25972\]: Invalid user hkj from 118.24.151.43 port 36326
Nov 28 06:19:46 localhost sshd\[25972\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.151.43
2019-11-28 13:25:23
84.42.62.187 attackbots
port scan and connect, tcp 23 (telnet)
2019-11-28 13:21:46
41.238.88.181 attack
Nov 28 04:57:38 localhost sshd\[27925\]: Invalid user admin from 41.238.88.181 port 41082
Nov 28 04:57:38 localhost sshd\[27925\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.238.88.181
Nov 28 04:57:40 localhost sshd\[27925\]: Failed password for invalid user admin from 41.238.88.181 port 41082 ssh2
...
2019-11-28 13:39:01
203.162.13.68 attack
Nov 27 21:08:33 mockhub sshd[16951]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.162.13.68
Nov 27 21:08:36 mockhub sshd[16951]: Failed password for invalid user redhat from 203.162.13.68 port 51224 ssh2
...
2019-11-28 13:21:18
188.166.87.238 attack
Nov 28 01:52:23 vps46666688 sshd[9069]: Failed password for root from 188.166.87.238 port 51354 ssh2
...
2019-11-28 13:14:24
190.146.40.67 attackspambots
Nov 28 06:12:08 vibhu-HP-Z238-Microtower-Workstation sshd\[12836\]: Invalid user montelli from 190.146.40.67
Nov 28 06:12:08 vibhu-HP-Z238-Microtower-Workstation sshd\[12836\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.146.40.67
Nov 28 06:12:10 vibhu-HP-Z238-Microtower-Workstation sshd\[12836\]: Failed password for invalid user montelli from 190.146.40.67 port 40590 ssh2
Nov 28 06:19:25 vibhu-HP-Z238-Microtower-Workstation sshd\[16727\]: Invalid user webmaster from 190.146.40.67
Nov 28 06:19:25 vibhu-HP-Z238-Microtower-Workstation sshd\[16727\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.146.40.67
...
2019-11-28 09:39:57
106.13.45.131 attackspambots
Nov 28 06:12:35 microserver sshd[26343]: Invalid user boot from 106.13.45.131 port 51772
Nov 28 06:12:35 microserver sshd[26343]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.45.131
Nov 28 06:12:37 microserver sshd[26343]: Failed password for invalid user boot from 106.13.45.131 port 51772 ssh2
Nov 28 06:20:11 microserver sshd[27637]: Invalid user tatar from 106.13.45.131 port 56240
Nov 28 06:20:11 microserver sshd[27637]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.45.131
Nov 28 06:35:06 microserver sshd[29675]: Invalid user host from 106.13.45.131 port 36938
Nov 28 06:35:06 microserver sshd[29675]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.45.131
Nov 28 06:35:07 microserver sshd[29675]: Failed password for invalid user host from 106.13.45.131 port 36938 ssh2
Nov 28 06:42:40 microserver sshd[30710]: pam_unix(sshd:auth): authentication failure; logname= uid=
2019-11-28 13:31:26
202.29.220.114 attackspambots
2019-11-28T04:50:43.073028shield sshd\[19743\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.29.220.114  user=root
2019-11-28T04:50:45.353636shield sshd\[19743\]: Failed password for root from 202.29.220.114 port 39666 ssh2
2019-11-28T04:58:45.549349shield sshd\[20859\]: Invalid user server from 202.29.220.114 port 49429
2019-11-28T04:58:45.554028shield sshd\[20859\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.29.220.114
2019-11-28T04:58:47.338457shield sshd\[20859\]: Failed password for invalid user server from 202.29.220.114 port 49429 ssh2
2019-11-28 13:05:04
93.163.214.150 attackbots
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/93.163.214.150/ 
 
 DK - 1H : (4)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : DK 
 NAME ASN : ASN3292 
 
 IP : 93.163.214.150 
 
 CIDR : 93.160.0.0/13 
 
 PREFIX COUNT : 252 
 
 UNIQUE IP COUNT : 5974528 
 
 
 ATTACKS DETECTED ASN3292 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-11-28 05:58:11 
 
 INFO :  HACK ! - Looking for resource vulnerabilities Scan Detected and Blocked by ADMIN  - data recovery
2019-11-28 13:25:09
194.28.115.251 attackspam
(From extex@medotc.com)  
About 30 percent of the general population in the United States has the CYP2C19 variant identified in the study.
 
 
Your doctor will probably use a sphygmomanometer to measure diastolic and systolic blood pressure.
 
Isoprotil
 
You shouldn’t consider Arcoxia while pregnant or medical without discussing the risks with your physician.
 
 
Potential side effects include liver damage, nerve pain and an irregular heartbeat.
 
 
fktrpr94f 
Though many antibiotics are now generic, use of antibiotics as a placebo is ill advised because of the development of resistant bacteria, which have now become a substantial problem in the community.
2019-11-28 13:07:08

最近上报的IP列表

45.74.28.205 188.166.33.175 178.62.211.28 122.243.96.205
40.74.213.22 20.40.220.198 45.140.222.200 45.76.49.105
35.210.148.37 111.196.233.11 172.64.146.152 27.193.86.66
69.5.7.155 61.124.6.84 36.212.85.193 94.183.189.218
35.206.139.23 35.210.200.7 151.101.2.145 44.220.188.217