CF1762285249808-tsm20251104152717

NSLIST.NET - templefire.net

Search for IP or hostnames:

templefire.net checked at 2025-11-04T19:40:49.793Z 260ms 142/142/142 100% R:15

templefire.net

MXaspmx2.googlemail.com
A2a00:1450:400b:c02::1b 🇮🇪 Google
PTRdj-in-f27.1e100.net
A172.253.116.27🇺🇸 Google
PTRdj-in-f27.1e100.net
MXaspmx3.googlemail.com
A2a00:1450:400c:c00::1a 🇧🇪 Google
PTRws-in-f26.1e100.net
PTRws-in-x1a.1e100.net
A173.194.76.27🇺🇸 Google
PTRws-in-f27.1e100.net
MXaspmx4.googlemail.com
A2607:f8b0:4023:3001::1a 🇺🇸 Google
PTRyulnkec-in-f26.1e100.net
A172.217.74.27🇺🇸 Google
PTRyulnkec-in-f27.1e100.net
MXaspmx5.googlemail.com
A2607:f8b0:4003:c30::1a 🇺🇸 Google
PTRyutulis-in-f26.1e100.net
A74.125.27.26🇺🇸 Google
PTRyutulis-in-f26.1e100.net
MXaspmx.l.google.com
A2607:f8b0:4004:c1f::1a 🇺🇸 Google
PTRpd-in-f26.1e100.net
A142.251.179.27🇺🇸 Google
PTRpd-in-f27.1e100.net
NSdns230.a.register.com
A216.21.231.230🇺🇸 AS19871
PTRdns230.a.register.com
NSdns239.b.register.com
A216.21.232.239🇺🇸 AS19871
PTRdns239.b.register.com
NSdns116.c.register.com
A216.21.235.116🇺🇸 AS19871
PTRdns116.c.register.com
NSdns177.d.register.com
A216.21.236.177🇺🇸 AS19871
PTRdns177.d.register.com
MXalt1.aspmx.l.google.com
A2a00:1450:400b:c02::1b 🇮🇪 Google
PTRdj-in-f27.1e100.net
A172.253.116.26🇺🇸 Google
PTRdj-in-f26.1e100.net
MXalt2.aspmx.l.google.com
A2a00:1450:400c:c00::1b 🇧🇪 Google
PTRws-in-f27.1e100.net
PTRws-in-x1b.1e100.net
A173.194.76.26🇺🇸 Google
PTRws-in-f26.1e100.net
A199.34.228.139🇺🇸 WEEBLY
PTRpages-custom-44.weebly.com

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

templefire.net resolves to a single IP: 199.34.228.139.

Other host names, for instance cmena.org, johnurquharticles.com, beverlyreinart.com, ifixrx.com and katmic.net share IP numbers with templefire.net.

templefire.net is delegated to four name servers: dns230.a.register.com, dns239.b.register.com, dns116.c.register.com and dns177.d.register.com.

templefire.net shares some name servers with other domains, for example planethyundai.com, outyard.net, cyoseeds.co.uk, amegy.us and neutrontelecom.com.

these name servers are often used with dns176.d.register.com, dns082.d.register.com, dns249.d.register.com, dns083.d.register.com, dns244.c.register.com, dns131.c.register.com, dns012.c.register.com, dns010.d.register.com, dns226.c.register.com and dns037.b.register.com.

Host names with a single IP

dns230.a.register.com resolves to 216.21.231.230

dns239.b.register.com resolves to 216.21.232.239

dns116.c.register.com resolves to 216.21.235.116

dns177.d.register.com resolves to 216.21.236.177

templefire.net is handled by seven mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, aspmx5.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.

templefire.net shares some mail servers with other domains, at least partially; for instance besz.pl, firebrandservicesgroup.com, pelotek.se, koon.dk and tbes.no.

these mail servers are commonly used alongside alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.

Host names with two IP numbers:

aspmx2.googlemail.com points to: 2a00:1450:400b:c02::1b and 172.253.116.27.

aspmx3.googlemail.com points to: 2a00:1450:400c:c00::1a and 173.194.76.27.

aspmx4.googlemail.com points to: 2607:f8b0:4023:3001::1a and 172.217.74.27.

aspmx5.googlemail.com points to: 2607:f8b0:4003:c30::1a and 74.125.27.26.

aspmx.l.google.com points to: 2607:f8b0:4004:c1f::1a and 142.251.179.27.

alt1.aspmx.l.google.com points to: 2a00:1450:400b:c02::1b and 172.253.116.26.

alt2.aspmx.l.google.com points to: 2a00:1450:400c:c00::1b and 173.194.76.26.

Host names that point to 2a00:1450:400b:c02::1b: aspmx2.googlemail.com and alt1.aspmx.l.google.com.

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