CF1759516687506-tsm20251003144104

WWW.ROBTEX.COM - kmkk.net

Search for IP or hostnames:

kmkk.net checked at 2025-10-03T18:38:07.489Z 838ms 123/123/123 100% R:18

kmkk.net

MXcluster.relay.agava.net
A31.31.194.240🇷🇺 AS-REGRU
PTRrelay.hosting.reg.ru
A31.31.194.241🇷🇺 AS-REGRU
PTRrelay.hosting.reg.ru
NSns1.agava.net.ru
A2a00:f940:4::47🇷🇺 AS-REGRU
PTRns1.reg.ru
A194.58.117.11🇷🇺 AS-REGRU
PTRns1.reg.ru
NSns2.agava.net.ru
A2a00:f940:5::190🇷🇺 AS-REGRU
PTRns2.reg.ru
A194.58.117.12🇷🇺 AS-REGRU
PTRns2.reg.ru
A2a03:4900:0:6037:80:78:250:14🇷🇺 AS-REGRU
PTRcp407.agava.net
A83.239.51.54🇷🇺 STC-AS

net

NSa.gtld-servers.net
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net

Starts with same word

Starts similarily

AI analysis

kmkk.net points to two IPs: 2a03:4900:0:6037:80:78:250:14 and 83.239.51.54.

Other host names, for instance superactivator.ru, belatour.ru, mamsluda.ru, cp407.agava.net and remote.serikova.ru share IP numbers with kmkk.net.

Two name servers ns1.agava.net.ru and ns2.agava.net.ru are delegated to kmkk.net.

kmkk.net uses the same name server configuration as other domains, such as ekom.spb.ru, dnd.com.ru, proghouse.ru, holywarp.com and tr-sozvezdie.ru.

Host names with two IPs:

ns1.agava.net.ru points to 2a00:f940:4::47 and 194.58.117.11.

ns2.agava.net.ru points to 2a00:f940:5::190 and 194.58.117.12.

kmkk.net is handled by a single mail server, cluster.relay.agava.net.

kmkk.net shares the same mail server setup as other domains, including ukhtoma.ru, steh.net, solclean.ru, scoota.ru and starfire.ru.

kmkk.net shares mail servers with other domains at least in part, for instance tsagroup.ru, ivconsult.ru, ateh.org, cp433.agava.net and twigy.ru.

these mail servers are commonly used alongside the mail servers aspmx.l.google.com.

Host name cluster.relay.agava.net points to IPs 31.31.194.240 and 31.31.194.241.

Perform reverse DNS lookup as well as normal forward DNS. Check Autonomous System Numbers (ASNs) and BGP connections between Internet Service Providers.
dbq

ySqDrhL CF johedugfp 2025-10-03