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 Kingdom

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 <<>> 212.18.248.42
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40633
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;212.18.248.42.			IN	A

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

;; Query time: 118 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jun 29 08:51:38 CST 2023
;; MSG SIZE  rcvd: 106
Host info
Host 42.248.18.212.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 42.248.18.212.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
165.227.114.134 attack
(sshd) Failed SSH login from 165.227.114.134 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jul  9 06:36:29 s1 sshd[14382]: Invalid user ejerez from 165.227.114.134 port 53752
Jul  9 06:36:31 s1 sshd[14382]: Failed password for invalid user ejerez from 165.227.114.134 port 53752 ssh2
Jul  9 06:53:58 s1 sshd[14742]: Invalid user tym from 165.227.114.134 port 56066
Jul  9 06:54:01 s1 sshd[14742]: Failed password for invalid user tym from 165.227.114.134 port 56066 ssh2
Jul  9 06:57:37 s1 sshd[14834]: Invalid user tokuda from 165.227.114.134 port 55508
2020-07-09 12:57:43
129.205.210.174 attackbotsspam
20/7/9@00:37:28: FAIL: Alarm-Network address from=129.205.210.174
...
2020-07-09 13:13:09
88.87.86.63 attack
Wordpress malicious attack:[sshd]
2020-07-09 13:22:00
217.219.116.116 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2020-07-09 13:03:50
42.3.149.127 attack
Port probing on unauthorized port 5555
2020-07-09 13:21:35
177.73.28.199 attack
Jul  9 06:53:26 ift sshd\[44526\]: Invalid user www from 177.73.28.199Jul  9 06:53:29 ift sshd\[44526\]: Failed password for invalid user www from 177.73.28.199 port 54698 ssh2Jul  9 06:55:36 ift sshd\[44928\]: Invalid user chl from 177.73.28.199Jul  9 06:55:38 ift sshd\[44928\]: Failed password for invalid user chl from 177.73.28.199 port 55164 ssh2Jul  9 06:57:39 ift sshd\[45221\]: Invalid user fgj from 177.73.28.199
...
2020-07-09 12:56:45
111.72.195.89 attack
Jul  9 06:21:29 srv01 postfix/smtpd\[20708\]: warning: unknown\[111.72.195.89\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul  9 06:25:05 srv01 postfix/smtpd\[27541\]: warning: unknown\[111.72.195.89\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul  9 06:25:16 srv01 postfix/smtpd\[27541\]: warning: unknown\[111.72.195.89\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul  9 06:25:33 srv01 postfix/smtpd\[27541\]: warning: unknown\[111.72.195.89\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul  9 06:25:52 srv01 postfix/smtpd\[27541\]: warning: unknown\[111.72.195.89\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-07-09 13:10:52
180.253.53.184 attack
nft/Honeypot/22/73e86
2020-07-09 13:02:24
218.92.0.148 attack
Jul  8 18:38:26 php1 sshd\[32439\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.148  user=root
Jul  8 18:38:28 php1 sshd\[32439\]: Failed password for root from 218.92.0.148 port 13489 ssh2
Jul  8 18:38:37 php1 sshd\[32442\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.148  user=root
Jul  8 18:38:39 php1 sshd\[32442\]: Failed password for root from 218.92.0.148 port 35778 ssh2
Jul  8 18:38:41 php1 sshd\[32442\]: Failed password for root from 218.92.0.148 port 35778 ssh2
2020-07-09 12:54:23
128.199.245.33 attack
Automatic report - Banned IP Access
2020-07-09 13:20:56
218.92.0.189 attackspam
07/09/2020-01:12:17.486289 218.92.0.189 Protocol: 6 ET SCAN Potential SSH Scan
2020-07-09 13:12:46
201.32.178.190 attack
Jul  9 06:16:18 piServer sshd[22917]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.32.178.190 
Jul  9 06:16:20 piServer sshd[22917]: Failed password for invalid user ann from 201.32.178.190 port 48855 ssh2
Jul  9 06:25:44 piServer sshd[24169]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.32.178.190 
...
2020-07-09 12:49:26
118.118.218.198 attack
Automated report (2020-07-09T11:57:03+08:00). User agent cited by malware detected at this address.
2020-07-09 13:29:49
210.108.149.116 attackspambots
Honeypot attack, port: 5555, PTR: PTR record not found
2020-07-09 13:25:44
106.13.64.132 attack
(sshd) Failed SSH login from 106.13.64.132 (CN/China/-): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD
2020-07-09 12:52:15

Recently Reported IPs

140.116.228.183 189.216.158.195 140.116.36.156 101.6.34.15
130.208.182.63 132.247.144.107 147.46.147.15 54.153.102.229
163.15.154.31 140.116.20.40 128.248.2.50 140.116.253.59
101.6.55.86 162.125.35.214 130.15.16.31 140.116.74.237
134.71.177.148 143.225.167.232 140.116.16.204 166.111.26.209