城市(city): Bogotá
省份(region): Bogota D.C.
国家(country): Colombia
运营商(isp): AT&T
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
#
# 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: 74.244.0.0 - 74.245.255.255
CIDR: 74.244.0.0/15
NetName: SS-2296
NetHandle: NET-74-244-0-0-1
Parent: NET74 (NET-74-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: SpaceX Services, Inc. (SS-2296)
RegDate: 2025-09-11
Updated: 2025-09-11
Ref: https://rdap.arin.net/registry/ip/74.244.0.0
OrgName: SpaceX Services, Inc.
OrgId: SS-2296
Address: 1 Rocket Rd
City: Hawthorne
StateProv: CA
PostalCode: 90250
Country: US
RegDate: 2019-06-24
Updated: 2024-11-25
Ref: https://rdap.arin.net/registry/entity/SS-2296
OrgTechHandle: STARL42-ARIN
OrgTechName: Starlink NOC
OrgTechPhone: +1-310-363-6000
OrgTechEmail: starlink-noc@spacex.com
OrgTechRef: https://rdap.arin.net/registry/entity/STARL42-ARIN
OrgNOCHandle: STARL42-ARIN
OrgNOCName: Starlink NOC
OrgNOCPhone: +1-310-363-6000
OrgNOCEmail: starlink-noc@spacex.com
OrgNOCRef: https://rdap.arin.net/registry/entity/STARL42-ARIN
OrgAbuseHandle: STARL38-ARIN
OrgAbuseName: Starlink Abuse
OrgAbusePhone: +1-310-363-6000
OrgAbuseEmail: starlink-abuse@spacex.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/STARL38-ARIN
OrgDNSHandle: STARL42-ARIN
OrgDNSName: Starlink NOC
OrgDNSPhone: +1-310-363-6000
OrgDNSEmail: starlink-noc@spacex.com
OrgDNSRef: https://rdap.arin.net/registry/entity/STARL42-ARIN
OrgRoutingHandle: STARL42-ARIN
OrgRoutingName: Starlink NOC
OrgRoutingPhone: +1-310-363-6000
OrgRoutingEmail: starlink-noc@spacex.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/STARL42-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 9.10.3-P4-Ubuntu <<>> 74.244.169.250
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16464
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;74.244.169.250. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026082201 1800 900 604800 86400
;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Aug 23 03:36:49 CST 2026
;; MSG SIZE rcvd: 107
250.169.244.74.in-addr.arpa domain name pointer customer.limaper1.isp.starlink.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
250.169.244.74.in-addr.arpa name = customer.limaper1.isp.starlink.com.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 45.160.180.241 | attack | Sep 3 18:43:27 mellenthin postfix/smtpd[20267]: NOQUEUE: reject: RCPT from unknown[45.160.180.241]: 554 5.7.1 Service unavailable; Client host [45.160.180.241] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/45.160.180.241; from= |
2020-09-05 03:42:50 |
| 64.64.233.198 | attackspam | 2020-09-03 17:28:54,001 fail2ban.actions [1312]: NOTICE [sshd] Ban 64.64.233.198 2020-09-03 17:52:05,067 fail2ban.actions [1312]: NOTICE [sshd] Ban 64.64.233.198 2020-09-03 18:20:57,013 fail2ban.actions [1312]: NOTICE [sshd] Ban 64.64.233.198 2020-09-03 18:43:35,784 fail2ban.actions [1312]: NOTICE [sshd] Ban 64.64.233.198 2020-09-03 19:06:09,639 fail2ban.actions [1312]: NOTICE [sshd] Ban 64.64.233.198 ... |
2020-09-05 03:37:27 |
| 49.234.96.210 | attack | 2020-09-05T01:48:30.371457hostname sshd[2275]: Invalid user zt from 49.234.96.210 port 51714 2020-09-05T01:48:32.242754hostname sshd[2275]: Failed password for invalid user zt from 49.234.96.210 port 51714 ssh2 2020-09-05T01:54:24.041539hostname sshd[3009]: Invalid user ftp1 from 49.234.96.210 port 52920 ... |
2020-09-05 03:31:12 |
| 103.136.9.253 | attack | 103.136.9.253 - - [04/Sep/2020:16:22:21 +0100] "POST /wp-login.php HTTP/1.1" 200 2046 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 103.136.9.253 - - [04/Sep/2020:16:22:23 +0100] "POST /wp-login.php HTTP/1.1" 200 2020 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 103.136.9.253 - - [04/Sep/2020:16:22:26 +0100] "POST /wp-login.php HTTP/1.1" 200 2019 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2020-09-05 03:30:53 |
| 113.98.193.58 | attackspambots | $f2bV_matches |
2020-09-05 03:34:50 |
| 192.241.239.54 | attackspambots | Port scan denied |
2020-09-05 03:18:24 |
| 113.140.80.174 | attack | Invalid user ali from 113.140.80.174 port 40853 |
2020-09-05 03:42:37 |
| 45.142.120.49 | attackspam | Sep 4 21:05:31 srv01 postfix/smtpd\[23814\]: warning: unknown\[45.142.120.49\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 4 21:05:44 srv01 postfix/smtpd\[19366\]: warning: unknown\[45.142.120.49\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 4 21:05:57 srv01 postfix/smtpd\[12650\]: warning: unknown\[45.142.120.49\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 4 21:05:57 srv01 postfix/smtpd\[23814\]: warning: unknown\[45.142.120.49\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 4 21:06:14 srv01 postfix/smtpd\[19366\]: warning: unknown\[45.142.120.49\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-09-05 03:12:47 |
| 39.153.252.94 | attackspam | Sep 2 19:43:54 www3-7 sshd[25235]: Did not receive identification string from 39.153.252.94 port 40327 Sep 3 11:50:01 www3-7 sshd[13399]: Did not receive identification string from 39.153.252.94 port 48125 Sep 3 11:50:08 www3-7 sshd[13482]: Invalid user user from 39.153.252.94 port 54153 Sep 3 11:50:09 www3-7 sshd[13482]: Connection closed by 39.153.252.94 port 54153 [preauth] Sep 3 11:51:03 www3-7 sshd[13486]: Invalid user oracle from 39.153.252.94 port 38673 Sep 3 11:51:07 www3-7 sshd[13486]: Connection closed by 39.153.252.94 port 38673 [preauth] Sep 3 11:51:09 www3-7 sshd[13545]: Invalid user admin from 39.153.252.94 port 49882 Sep 3 11:51:10 www3-7 sshd[13545]: Connection closed by 39.153.252.94 port 49882 [preauth] Sep 3 11:51:19 www3-7 sshd[13547]: Invalid user test from 39.153.252.94 port 53810 Sep 3 11:51:27 www3-7 sshd[13547]: Connection closed by 39.153.252.94 port 53810 [preauth] Sep 3 11:51:50 www3-7 sshd[13554]: Invalid user hadoop from 39.153.2........ ------------------------------- |
2020-09-05 03:34:11 |
| 201.63.224.82 | attack | Honeypot attack, port: 445, PTR: 201-63-224-82.customer.tdatabrasil.net.br. |
2020-09-05 03:14:00 |
| 192.42.116.20 | attackbots | Unauthorised connection attempt detected at AUO NODE 4. System is sshd. Protected by AUO Stack Web Application Firewall (WAF) |
2020-09-05 03:14:30 |
| 213.141.131.22 | attackbots | Sep 4 20:42:09 santamaria sshd\[21094\]: Invalid user vs from 213.141.131.22 Sep 4 20:42:09 santamaria sshd\[21094\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.141.131.22 Sep 4 20:42:10 santamaria sshd\[21094\]: Failed password for invalid user vs from 213.141.131.22 port 41866 ssh2 ... |
2020-09-05 03:13:01 |
| 218.92.0.223 | attack | Sep 4 16:07:25 vps46666688 sshd[942]: Failed password for root from 218.92.0.223 port 51239 ssh2 Sep 4 16:07:38 vps46666688 sshd[942]: error: maximum authentication attempts exceeded for root from 218.92.0.223 port 51239 ssh2 [preauth] ... |
2020-09-05 03:09:00 |
| 106.54.133.103 | attackspam | Invalid user prueba from 106.54.133.103 port 38544 |
2020-09-05 03:08:40 |
| 175.101.156.126 | attackbots | IP 175.101.156.126 attacked honeypot on port: 1433 at 9/3/2020 9:43:16 AM |
2020-09-05 03:43:15 |