NSLIST.NET - ftl.name

Search for IP or hostnames:

ftl.name checked at 2025-09-07T08:42:40.116Z 242ms 182/182/182 100% R:17

`ftl.name`

NS	`ns1.reg.ru`
		A	2a00:f940:9::1:1 ^{🇷🇺 AS-REGRU}
		A	2a00:f940:9::2:1 ^{🇷🇺 AS-REGRU}
		A	176.99.13.11^{🇷🇺 AS-REGRU}
			PTR	`ns1.reg.ru`
		A	176.99.13.13^{🇷🇺 AS-REGRU}
			PTR	`ns1.reg.ru`
		A	176.99.13.15^{🇷🇺 AS-REGRU}
			PTR	`ns1.reg.ru`
		A	176.99.13.17^{🇷🇺 AS-REGRU}
			PTR	`ns1.reg.ru`
		A	194.58.117.11^{🇷🇺 AS-REGRU}
			PTR	`ns1.reg.ru`
		A	194.58.117.13^{🇷🇺 AS-REGRU}
			PTR	`ns1.reg.ru`
		A	194.58.117.15^{🇷🇺 AS-REGRU}
			PTR	`ns1.reg.ru`
		A	194.58.117.17^{🇷🇺 AS-REGRU}
			PTR	`ns1.reg.ru`
NS	`ns2.reg.ru`
		A	2a00:f940:9::1:2 ^{🇷🇺 AS-REGRU}
		A	2a00:f940:9::2:2 ^{🇷🇺 AS-REGRU}
		A	176.99.13.12^{🇷🇺 AS-REGRU}
			PTR	`ns2.reg.ru`
		A	176.99.13.14^{🇷🇺 AS-REGRU}
			PTR	`ns2.reg.ru`
		A	176.99.13.16^{🇷🇺 AS-REGRU}
			PTR	`ns2.reg.ru`
		A	176.99.13.18^{🇷🇺 AS-REGRU}
			PTR	`ns2.reg.ru`
		A	194.58.117.12^{🇷🇺 AS-REGRU}
			PTR	`ns2.reg.ru`
		A	194.58.117.14^{🇷🇺 AS-REGRU}
			PTR	`ns2.reg.ru`
		A	194.58.117.16^{🇷🇺 AS-REGRU}
			PTR	`ns2.reg.ru`
		A	194.58.117.18^{🇷🇺 AS-REGRU}
			PTR	`ns2.reg.ru`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c1b::1a ^{🇺🇸 Google}
			PTR	`wv-in-f26.1e100.net`
		A	142.251.16.27^{🇺🇸 Google}
			PTR	`bl-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:400b:c02::1a ^{🇮🇪 Google}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google}
			PTR	`dj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`
		A	2a00:1450:400c:c00::1a ^{🇧🇪 Google}
			PTR	`ws-in-f26.1e100.net`
			PTR	`ws-in-x1a.1e100.net`
		A	173.194.76.27^{🇺🇸 Google}
			PTR	`ws-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`
		A	2a00:1450:4025:402::1b ^{🇳🇱 Google}
			PTR	`rb-in-f27.1e100.net`
		A	142.250.102.27^{🇺🇸 Google}
			PTR	`rb-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`
		A	2a00:1450:4013:c1c::1b ^{🇳🇱 Google}
			PTR	`yugrqog-in-f27.1e100.net`
		A	192.178.156.26^{🇺🇸 Google}
			PTR	`yugrqog-in-f26.1e100.net`
A	91.189.114.29^{🇷🇺 RU-CENTER AS48287}
		PTR	`wcarp.hosting.nic.ru`

`name`

	NS	`ac1.nstld.com`
	NS	`ac2.nstld.com`
	NS	`ac3.nstld.com`
	NS	`ac4.nstld.com`

Up
`lms.ftl.name`
`lisa.ftl.name`

Starts with same word
`ftl.com.br`
`ftl.cz`
`ftl.nu`
`ftl.net`
`ftl.se`
`ftl.es`
`ftl.fl.us`
`ftl.blue`
`ftl.com.my`
`ftl.mu`
`ftl.events`
`ftl.com`
`ftl.canva-apps.cn`
`ftl.cn`
`ftl.co`
`ftl.si`
`ftl.kiev.ua`
`ftl.no`
`ftl.ie`
`ftl.us`
`ftl.name`
`ftl.ua`
`ftl.biz`
`ftl.vn`
`ftl.kz`
`ftl.tv`
`ftl.dk`
`ftl.be`
`ftl.lk`
`ftl.kherson.ua`
`ftl.co.nz`
`ftl.cl`
`ftl.me`
`ftl.at`
`ftl.com.ua`
`ftl.info`
`ftl.dev`
`ftl.co.jp`
`ftl.com.vn`
`ftl.ru`
`ftl.pub`
`ftl.wtf`
`ftl.cc`
`ftl.coach`
`ftl.systems`
`ftl.pl`
`ftl.lv`
`ftl.it`
`ftl.in`
`ftl.ks.ua`
`ftl.if.ua`

Starts similarily
`tfl.dev`
`ftl.dev`
`tlf.com.tn`
`ftl.co.jp`
`ftl.com.vn`
`tfl.solutions`
`tlf.directory`
`tfl.com.fj`
`ftl.ru`
`ftl.pub`
`flt.co`
`tfl.gov.uk`
`ftl.wtf`
`ftl.cc`
`lft.co.nz`
`flt.cn`
`ftl.coach`
`flt.nu`
`ltf.fi`
`ltf.ca`
`ftl.systems`
`ltf.in.ua`
`flt.lv`
`tfl.ca`
`tlf.us`
`tlf.gov.cn`
`tfl.tokyo`
`tfl.it`
`lft.lt`
`ftl.pl`
`ftl.lv`
`tfl.uno`
`ftl.it`
`ltf.com.vn`
`ftl.in`
`tfl.pl`
`lft.fi`
`ltf.org.pl`
`ftl.ks.ua`
`ltf.com`
`ltf.com.br`
`ftl.if.ua`
`flt.cl`
`flt.io`
`tfl.jp`
`tfl.su`
`flt.cz`
`tlf.me`
`ltf.no`
`tfl.am`
`tfl.digital`
`tlf.bm`
`ltf.it`
`flt.ca`
`tfl.gr`
`lft.in`
`tfl.info`
`flt.biz`
`ltf.be`
`ftl.com.br`
`flt.krasnik.pl`
`flt.org`
`lft.se`
`lft.de`
`flt.ru`
`flt.co.za`
`tfl.dk`
`tlf.md`
`flt.eu`
`ftl.cz`
`ltf.com.ua`
`flt.at`
`tlf.fi`
`ftl.nu`
`lft.ca`
`ftl.net`
`tlf.se`
`ftl.se`
`ftl.es`
`ftl.fl.us`
`tfl.com`
`ftl.blue`
`tfl.tours`
`tfl.k12.tr`
`tlf.at`
`tfl.coffee`
`ftl.com.my`
`ltf.pl`
`tfl.nl`
`ftl.mu`
`lft.es`
`tfl.at`
`lft.to`
`tfl.no`
`tfl.us`
`tfl.co`
`tfl.mx`
`tlf.ch`
`lft.com.br`
`tfl.ru`

AI analysis

lms.ftl.name and lisa.ftl.name are children of ftl.name.

91.189.114.29 is the IP number that ftl.name points to.

IP numbers are shared between ftl.name and other host names such as lasen.ru, artofwar.net.ru, vialco.ru, neopage.ru, and lts-uv.ru.

Two name servers, ns1.reg.ru and ns2.reg.ru, have been delegated to ftl.name.

The name server setup of ftl.name is identical to that of other domains such as bamper.pro, voprosotvet.ru, eg-kr.ru, targettop.ru, and modamania-online.ru.

Ten IP numbers are pointed to by ns1.reg.ru: 2a00:f940:9::1:1, 2a00:f940:9::2:1, 176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15, and 194.58.117.17. Another set of ten IP numbers are pointed to by ns2.reg.ru: 2a00:f940:9::1:2, 2a00:f940:9::2:2, 176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16, and 194.58.117.18.

Five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com, manage ftl.name.

Domains such as abt-archi.com, colesptlax.edu.mx, smdaylesford.catholic.edu.au, pro-intro.com, and mdima.ru share at least some mail servers partially with ftl.name.

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, aspmx5.googlemail.com, smdaylesford-catholic-edu-au.mail.protection.outlook.com, and jvpcvx6xrpvvnomasu2q4qrfakv62a7zqrrwvcez3gmlfybb4laq.mx-verification.google.com are commonly used in conjunction.

aspmx.l.google.com, 2607:f8b0:4004:c1b::1a, and 142.251.16.27 are associated.

alt1.aspmx.l.google.com, 2a00:1450:400b:c02::1a, and 172.253.116.26 are associated.

alt2.aspmx.l.google.com, 2a00:1450:400c:c00::1a, and 173.194.76.27 are associated.

alt3.aspmx.l.google.com, 2a00:1450:4025:402::1b, and 142.250.102.27 are associated.

alt4.aspmx.l.google.com, 2a00:1450:4013:c1c::1b, and 192.178.156.26 are associated.

dbq