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 <<>> 168.42.249.74
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42653
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;168.42.249.74. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024121101 1800 900 604800 86400
;; Query time: 41 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Dec 12 07:04:09 CST 2024
;; MSG SIZE rcvd: 106Host 74.249.42.168.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 74.249.42.168.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 196.11.231.220 | attackbots | DATE:2019-07-22 19:39:00, IP:196.11.231.220, PORT:ssh brute force auth on SSH service (patata) |
2019-07-23 05:11:45 |
| 85.154.207.23 | attack | Automatic report - Port Scan Attack |
2019-07-23 04:54:30 |
| 216.218.206.0 | attack | Attempting to establish IPSec tunnel multiple times. |
2019-07-23 04:36:44 |
| 46.35.244.227 | attack | [portscan] Port scan |
2019-07-23 04:35:47 |
| 208.100.26.235 | attackbots | Automatic report - Banned IP Access |
2019-07-23 04:45:43 |
| 175.214.59.249 | attackspambots | /var/log/messages:Jul 22 12:44:42 sanyalnet-cloud-vps audispd: node=sanyalnet-cloud-vps.freeddns.org type=CRYPTO_SESSION msg=audhostname(1563799482.176:63978): pid=31066 uid=0 auid=4294967295 ses=4294967295 msg='op=start direction=from-server cipher=aexxxxxxx28-ctr ksize=128 mac=hmac-sha2-256 pfs=ecdh-sha2-nistp256 spid=31067 suid=74 rport=33500 laddr=104.167.106.93 lport=22 exe="/usr/sbin/sshd" hostname=? addr=175.214.59.249 terminal=? res=success' /var/log/messages:Jul 22 12:44:42 sanyalnet-cloud-vps audispd: node=sanyalnet-cloud-vps.freeddns.org type=CRYPTO_SESSION msg=audhostname(1563799482.177:63979): pid=31066 uid=0 auid=4294967295 ses=4294967295 msg='op=start direction=from-client cipher=aexxxxxxx28-ctr ksize=128 mac=hmac-sha2-256 pfs=ecdh-sha2-nistp256 spid=31067 suid=74 rport=33500 laddr=104.167.106.93 lport=22 exe="/usr/sbin/sshd" hostname=? addr=175.214.59.249 terminal=? res=success' /var/log/messages:Jul 22 12:44:42 sanyalnet-cloud-vps audispd: node=sanyal........ ------------------------------- |
2019-07-23 05:10:08 |
| 87.120.50.226 | attack | Honeypot attack, port: 23, PTR: PTR record not found |
2019-07-23 04:54:09 |
| 201.152.23.172 | attackspam | @LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-07-20 15:40:21,701 INFO [shellcode_manager] (201.152.23.172) no match, writing hexdump (a8f613a17b18a7178a33526f655d7c61 :14030) - SMB (Unknown) |
2019-07-23 04:44:49 |
| 179.108.105.126 | attack | Jul 22 17:34:00 Proxmox sshd\[6894\]: Invalid user ra from 179.108.105.126 port 37048 Jul 22 17:34:00 Proxmox sshd\[6894\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.108.105.126 Jul 22 17:34:02 Proxmox sshd\[6894\]: Failed password for invalid user ra from 179.108.105.126 port 37048 ssh2 Jul 22 17:46:38 Proxmox sshd\[20334\]: Invalid user techadmin from 179.108.105.126 port 60436 Jul 22 17:46:38 Proxmox sshd\[20334\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.108.105.126 Jul 22 17:46:40 Proxmox sshd\[20334\]: Failed password for invalid user techadmin from 179.108.105.126 port 60436 ssh2 |
2019-07-23 04:56:30 |
| 51.39.66.99 | attack | LGS,WP GET /wp-login.php |
2019-07-23 04:39:20 |
| 103.52.16.35 | attack | Jul 22 16:17:35 icinga sshd[5298]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.52.16.35 Jul 22 16:17:37 icinga sshd[5298]: Failed password for invalid user omc from 103.52.16.35 port 52350 ssh2 ... |
2019-07-23 04:40:06 |
| 198.245.72.70 | attackbotsspam | (From cath@mail.kathreadwrites.net) Hello I'm an SEO copywriter & wanted to share a quick ranking case study with you. Google Loves the RIGHT WORDS in the RIGHT PLACE. I Got It Wrong. I changed 8 words on a page...and you won't believe what happened. So I wrote a case study about it. Read it here: https://kathreadwrites.net/onpage-us/ ? Put the WRONG WORDS in the WRONG PLACE and you will not rank. PERIOD. I hope this case study inspires you to check out your own on-page optimization. Be Amazing Cath P.S. To get in touch, please use the contact form on my website instead of emailing me. Unsubscribe |
2019-07-23 04:41:19 |
| 208.100.26.237 | attackspambots | Automatic report - Banned IP Access |
2019-07-23 05:06:06 |
| 114.35.118.48 | attackbots | @LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-07-20 15:40:28,650 INFO [shellcode_manager] (114.35.118.48) no match, writing hexdump (747b6ed3a8c7631412e18cda9cf0e813 :1933276) - MS17010 (EternalBlue) |
2019-07-23 04:23:01 |
| 200.52.36.61 | attack | Automatic report - Port Scan Attack |
2019-07-23 04:47:56 |