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: unknown

Region: unknown

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:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.98.127.42
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63493
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.98.127.42.			IN	A

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

;; Query time: 107 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jul 08 11:38:58 CST 2025
;; MSG SIZE  rcvd: 106
Host info
42.127.98.104.in-addr.arpa domain name pointer a104-98-127-42.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
42.127.98.104.in-addr.arpa	name = a104-98-127-42.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
23.254.203.51 attack
Invalid user wsh from 23.254.203.51 port 50980
2019-10-25 01:38:52
165.227.97.108 attackbots
Tried sshing with brute force.
2019-10-25 01:53:45
159.65.88.161 attackbotsspam
SSH bruteforce (Triggered fail2ban)
2019-10-25 01:55:20
138.97.94.1 attack
Invalid user admin from 138.97.94.1 port 51086
2019-10-25 01:59:29
188.225.11.158 attack
Invalid user raimax from 188.225.11.158 port 52002
2019-10-25 01:48:48
106.12.24.1 attackspambots
Automatic report - Banned IP Access
2019-10-25 01:24:16
104.244.77.210 attackbots
SSH Bruteforce
2019-10-25 01:24:29
86.35.42.74 attack
Oct 24 13:41:10 ws22vmsma01 sshd[223677]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.35.42.74
...
2019-10-25 01:29:41
111.231.82.143 attackbotsspam
SSH bruteforce
2019-10-25 01:20:18
58.254.132.239 attackbotsspam
Oct 24 19:28:35 lnxded64 sshd[10991]: Failed password for root from 58.254.132.239 port 63624 ssh2
Oct 24 19:28:35 lnxded64 sshd[10991]: Failed password for root from 58.254.132.239 port 63624 ssh2
2019-10-25 01:32:58
94.242.171.201 attack
2019-01-25 16:40:58 H=\(201.net-94.242.171.kaluga.ru\) \[94.242.171.201\]:14041 I=\[193.107.88.166\]:25 F=\ rejected RCPT \: Sender verify failed
2019-01-25 16:41:43 H=\(201.net-94.242.171.kaluga.ru\) \[94.242.171.201\]:14294 I=\[193.107.88.166\]:25 F=\ rejected RCPT \: Sender verify failed
2019-01-25 16:42:07 H=\(201.net-94.242.171.kaluga.ru\) \[94.242.171.201\]:14395 I=\[193.107.88.166\]:25 F=\ rejected RCPT \: Sender verify failed
...
2019-10-25 01:27:19
106.12.218.175 attack
Invalid user fork from 106.12.218.175 port 55306
2019-10-25 01:20:36
174.115.45.16 attackbotsspam
Invalid user max from 174.115.45.16 port 53804
2019-10-25 01:52:54
146.185.149.245 attackbotsspam
Oct 24 18:03:15 ArkNodeAT sshd\[23940\]: Invalid user admin from 146.185.149.245
Oct 24 18:03:15 ArkNodeAT sshd\[23940\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=146.185.149.245
Oct 24 18:03:17 ArkNodeAT sshd\[23940\]: Failed password for invalid user admin from 146.185.149.245 port 34693 ssh2
2019-10-25 01:57:37
178.116.159.202 attack
Oct 24 18:54:47 ks10 sshd[9775]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.116.159.202 
Oct 24 18:54:49 ks10 sshd[9775]: Failed password for invalid user zimbra from 178.116.159.202 port 58257 ssh2
...
2019-10-25 01:51:47

Recently Reported IPs

111.78.233.198 108.219.93.14 106.62.204.25 47.96.100.78
20.14.94.72 46.146.84.138 141.98.11.116 77.110.113.234
91.90.120.163 51.68.244.174 201.214.46.229 93.117.9.137
77.238.122.157 170.127.200.12 168.158.200.0 91.56.89.224
172.203.245.49 42.239.4.59 147.185.132.80 44.244.128.122