City: unknown
Region: unknown
Country: United States of America (the)
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 98.99.127.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35440
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;98.99.127.1. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021102 1800 900 604800 86400
;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 12 11:40:31 CST 2025
;; MSG SIZE rcvd: 104b'Host 1.127.99.98.in-addr.arpa not found: 2(SERVFAIL)
'b'
Authoritative answers can be found from:
'| IP | Type | Details | Datetime |
|---|---|---|---|
| 158.69.195.175 | attackspambots | Dec 12 08:09:12 herz-der-gamer sshd[25126]: Invalid user jl from 158.69.195.175 port 49740 Dec 12 08:09:12 herz-der-gamer sshd[25126]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.195.175 Dec 12 08:09:12 herz-der-gamer sshd[25126]: Invalid user jl from 158.69.195.175 port 49740 Dec 12 08:09:14 herz-der-gamer sshd[25126]: Failed password for invalid user jl from 158.69.195.175 port 49740 ssh2 ... |
2019-12-12 17:58:54 |
| 197.155.234.157 | attackbotsspam | Dec 12 10:39:00 eventyay sshd[24267]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.155.234.157 Dec 12 10:39:02 eventyay sshd[24267]: Failed password for invalid user humboldt from 197.155.234.157 port 54582 ssh2 Dec 12 10:46:12 eventyay sshd[24488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.155.234.157 ... |
2019-12-12 17:55:49 |
| 213.154.3.69 | attack | Port Scan |
2019-12-12 18:00:45 |
| 114.98.232.165 | attackspambots | 2019-12-12T11:14:11.191568vps751288.ovh.net sshd\[4473\]: Invalid user boynton from 114.98.232.165 port 58902 2019-12-12T11:14:11.198333vps751288.ovh.net sshd\[4473\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.98.232.165 2019-12-12T11:14:13.539106vps751288.ovh.net sshd\[4473\]: Failed password for invalid user boynton from 114.98.232.165 port 58902 ssh2 2019-12-12T11:23:25.038510vps751288.ovh.net sshd\[4571\]: Invalid user semus from 114.98.232.165 port 54076 2019-12-12T11:23:25.047255vps751288.ovh.net sshd\[4571\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.98.232.165 |
2019-12-12 18:27:14 |
| 113.184.105.129 | attackbots | Unauthorized connection attempt from IP address 113.184.105.129 on Port 445(SMB) |
2019-12-12 18:15:24 |
| 59.72.122.148 | attackbots | Dec 12 11:12:28 ns381471 sshd[29004]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.72.122.148 Dec 12 11:12:30 ns381471 sshd[29004]: Failed password for invalid user fain from 59.72.122.148 port 44974 ssh2 |
2019-12-12 18:27:56 |
| 187.32.227.205 | attackbotsspam | Automatic report: SSH brute force attempt |
2019-12-12 18:08:13 |
| 104.129.4.229 | attackspam | (From eric@talkwithcustomer.com) Hello knutsonchiropractic.com, People ask, “why does TalkWithCustomer work so well?” It’s simple. TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time. - NOT one week, two weeks, three weeks after they’ve checked out your website knutsonchiropractic.com. - NOT with a form letter style email that looks like it was written by a bot. - NOT with a robocall that could come at any time out of the blue. TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU. They kick off the conversation. They take that first step. They ask to hear from you regarding what you have to offer and how it can make their life better. And it happens almost immediately. In real time. While they’re still looking over your website knutsonchiropractic.com, trying to make up their mind whether you are right for them. When you connect with them at that very moment it’s the ultimate in Perfect Timing – |
2019-12-12 18:03:23 |
| 50.236.148.254 | attack | 50.236.148.254 - - [12/Dec/2019:07:26:36 +0100] "GET /awstats.pl?config=oraux.pnzone.net&lang=en&output=main HTTP/1.0" 404 280 "https://oraux.pnzone.net/awstats.pl?config=carpetcleanerkalamazoo.com&lang=en&output=main" "Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; IE8Mercury; rv:11.0) like Gecko" |
2019-12-12 18:19:41 |
| 185.143.223.128 | attackbotsspam | Dec 12 13:06:56 debian-2gb-vpn-nbg1-1 kernel: [523596.260664] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=185.143.223.128 DST=78.46.192.101 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=1144 PROTO=TCP SPT=59481 DPT=10522 WINDOW=1024 RES=0x00 SYN URGP=0 |
2019-12-12 18:07:34 |
| 115.74.223.60 | attackspambots | Helo |
2019-12-12 17:57:07 |
| 83.171.107.216 | attackspambots | $f2bV_matches |
2019-12-12 18:27:42 |
| 86.188.246.2 | attackbotsspam | Dec 12 10:16:03 server sshd\[10865\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.188.246.2 user=root Dec 12 10:16:06 server sshd\[10865\]: Failed password for root from 86.188.246.2 port 56064 ssh2 Dec 12 10:23:17 server sshd\[12870\]: Invalid user lipson from 86.188.246.2 Dec 12 10:23:17 server sshd\[12870\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.188.246.2 Dec 12 10:23:19 server sshd\[12870\]: Failed password for invalid user lipson from 86.188.246.2 port 39651 ssh2 ... |
2019-12-12 18:18:42 |
| 67.207.88.180 | attackspambots | Dec 12 08:27:51 jane sshd[12694]: Failed password for root from 67.207.88.180 port 35372 ssh2 Dec 12 08:33:22 jane sshd[16537]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.207.88.180 ... |
2019-12-12 18:12:42 |
| 94.23.218.10 | attackspam | 5x Failed Password |
2019-12-12 18:26:44 |