rmtelegram.com - dns.ninja

`rmtelegram.com`

DNSSEC	⚠️ Not signed
A	96.45.82.16^{🇺🇸 Tiggee96.45.82.0/24 route 96.45.82.0/24}
		PTR	`redirection.dnsmadeeasy.com`
A	96.45.82.201^{🇺🇸 Tiggee96.45.82.0/24 route 96.45.82.0/24}
A	96.45.83.36^{🇺🇸 Tiggee96.45.83.0/24 route 96.45.83.0/24}
A	96.45.83.189^{🇺🇸 Tiggee96.45.83.0/24 route 96.45.83.0/24}
NS	`ns10.digicertdns.com` ⭐
		A	2600:1800::1:1f^{🇺🇸 Tiggee2600:1800::/48 DNS Made Easy anycast network}
			PTR	`ns10.digicertdns.com`
		A	208.94.148.159^{🇺🇸 Tiggee208.94.148.0/24 DNS Made Easy anycast network}
			PTR	`ns10.digicertdns.com`
NS	`ns11.digicertdns.com`
		A	2600:1801:1::1:1f^{🇺🇸 Tiggee2600:1801:1::/48 DNS Made Easy anycast network}
			PTR	`ns11.digicertdns.com`
		A	208.80.124.159^{🇺🇸 Tiggee208.80.124.0/24 DNS Made Easy anycast network}
			PTR	`ns11.digicertdns.com`
NS	`ns12.digicertdns.com`
		A	2600:1802:2::1:1f^{🇺🇸 Tiggee2600:1802:2::/48 DNS Made Easy anycast network}
			PTR	`ns12.digicertdns.com`
		A	208.80.126.159^{🇺🇸 Tiggee208.80.126.0/24 DNS Made Easy anycast network}
			PTR	`ns12.digicertdns.com`
NS	`ns13.digicertdns.net`
		A	2600:1801:3::1:1f^{🇺🇸 Tiggee2600:1801:3::/48 DNS Made Easy anycast network}
			PTR	`ns13.digicertdns.net`
		A	208.80.125.159^{🇺🇸 Tiggee208.80.125.0/24 DNS Made Easy anycast network}
			PTR	`ns13.digicertdns.net`
NS	`ns14.digicertdns.net`
		A	2600:1802:4::1:1f^{🇺🇸 Tiggee2600:1802:4::/48 DNS Made Easy anycast network}
			PTR	`ns14.digicertdns.net`
		A	208.80.127.159^{🇺🇸 Tiggee208.80.127.0/24 DNS Made Easy anycast network}
			PTR	`ns14.digicertdns.net`
NS	`ns15.digicertdns.net`
		A	2600:1800:8::1:1f^{🇺🇸 Tiggee2600:1800:8::/48 DNS Made Easy anycast network}
			PTR	`ns15.digicertdns.net`
		A	208.94.149.159^{🇺🇸 Tiggee208.94.149.0/24 DNS Made Easy anycast network}
			PTR	`ns15.digicertdns.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c21::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pe-in-f26.1e100.net`
		A	142.251.16.26^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`v=spf1 a:smtp.nccooke.com a:smtp.apgenc.com a:smtp.ncweeklies.com a:zimbra.nc...`
TXT	`v=DMARC1; p=none; rua=mailto:dmarc@rmtelegram.com; ruf=mailto:dmarc@rmtelegra...`
TXT	`google-site-verification=DSIU7Lihn1iY_B0roqWrmsv_W4hjw1gJugNt3EbHOQ4`
SOA	`ns10.digicertdns.com`dns@digicertdns.com 2009-01-01 #14

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1786450999

Subdomains

smtp.rmtelegram.com

Same first word

rmtelegram.com

Similar names

telegramrm.com

telemrgram.cc

mrtelegram.com

DNS History

20 records (15 active, 5 former)

●NSns10.digicertdns.com2026-02-24 → 2026-08-11 · 3 obs

○ 2017-07-10 08:02:00
● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

●NSns11.digicertdns.com2026-02-24 → 2026-08-11 · 3 obs

○ 2017-07-10 08:02:00
● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

●NSns12.digicertdns.com2026-02-24 → 2026-08-11 · 3 obs

○ 2017-07-10 08:02:00
● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

●NSns13.digicertdns.net2026-02-24 → 2026-08-11 · 3 obs

○ 2017-07-10 08:02:00
● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

●NSns14.digicertdns.net2026-02-24 → 2026-08-11 · 3 obs

○ 2017-07-10 08:02:00
● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

●NSns15.digicertdns.net2026-02-24 → 2026-08-11 · 3 obs

○ 2017-07-10 08:02:00
● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

○NSns57.domaincontrol.com2015-07-10 → 2017-07-10 · 4 obs

● 2015-07-10 03:34:28
● 2017-07-10 08:02:00
○ 2026-02-24 19:05:24
○ 2026-08-11 12:24:32

○NSns58.domaincontrol.com2015-07-10 → 2017-07-10 · 4 obs

● 2015-07-10 03:34:28
● 2017-07-10 08:02:00
○ 2026-02-24 19:05:24
○ 2026-08-11 12:24:32

●MXalt1.aspmx.l.google.com2026-02-24 → 2026-08-11 · 3 obs

○ 2017-07-10 08:02:00
● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

●MXalt2.aspmx.l.google.com2026-02-24 → 2026-08-11 · 3 obs

○ 2017-07-10 08:02:00
● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

●MXalt3.aspmx.l.google.com2026-02-24 → 2026-08-11 · 3 obs

○ 2017-07-10 08:02:00
● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

●MXalt4.aspmx.l.google.com2026-02-24 → 2026-08-11 · 3 obs

○ 2017-07-10 08:02:00
● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

●MXaspmx.l.google.com2026-02-24 → 2026-08-11 · 3 obs

○ 2017-07-10 08:02:00
● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

○MXd81543a.ess.barracudanetworks.com2016-02-08 → 2017-07-10 · 5 obs

○ 2015-07-10 03:34:28
● 2016-02-08 19:15:36
● 2017-07-10 08:02:00
○ 2026-02-24 19:05:24
○ 2026-08-11 12:24:32

○MXd81543b.ess.barracudanetworks.com2016-02-08 → 2017-07-10 · 5 obs

○ 2015-07-10 03:34:28
● 2016-02-08 19:15:36
● 2017-07-10 08:02:00
○ 2026-02-24 19:05:24
○ 2026-08-11 12:24:32

○MXsmtp.rmtelegram.com2015-07-10 → 2017-07-10 · 4 obs

● 2015-07-10 03:34:28
● 2017-07-10 08:02:00
○ 2026-02-24 19:05:24
○ 2026-08-11 12:24:32

●A96.45.82.162026-02-24 → 2026-08-11 · 2 obs

● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

●A96.45.82.2012026-02-24 → 2026-08-11 · 2 obs

● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

●A96.45.83.1892026-02-24 → 2026-08-11 · 2 obs

● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

●A96.45.83.362026-02-24 → 2026-08-11 · 2 obs

● 2026-02-24 19:05:24
● 2026-08-11 12:24:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, k.gtld-servers.net, f.gtld-servers.net, e.gtld-servers.net...	-
rmtelegram.com	ns10.digicertdns.com, ns11.digicertdns.com, ns12.digicertdns.com, ns13.digicertdns.net...	6 records

✅ Authoritative Response

Server:208.94.148.159

NS records: ns10.digicertdns.com, ns11.digicertdns.com, ns12.digicertdns.com, ns13.digicertdns.net, ns14.digicertdns.net, ns15.digicertdns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for rmtelegram.com (unsigned zone)

⏱️ Timing

Total: 1839ms | Queries: -

📄 Records

Type	Count	Sample Data
A	4	`96.45.83.36, 96.45.82.201...`
NS	6	`ns10.digicertdns.com, ns13.digicertdns.net...`
MX	5	`alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)...`
TXT	3	`v=spf1 a:smtp.nccooke.com a:smtp.apgenc., google-site-verification=DSIU7Lihn1iY_B0...`
SOA	1	`ns10.digicertdns.com dns.digicertdns.com`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns10.digicertdns.com, ns10.digicertdns.com, ns11.digicertdns.com...)

Analysis

Hierarchy

The domain smtp.rmtelegram.com falls under the parent rmtelegram.com.

IP Addresses

rmtelegram.com points to the four IP addresses 96.45.82.16, 96.45.82.201, 96.45.83.36 and 96.45.83.189.

Two other host names, along with billcorleysongs.com, ldcb.net and 203.131.clockworkins.com, also share IP numbers with rmtelegram.com.

Name Servers

rmtelegram.com delegates authority to 6 name servers: ns10.digicertdns.com, ns11.digicertdns.com, ns12.digicertdns.com plus 3 other.

At least some of rmtelegram.com's name servers are shared with other domains, for example rescueoneclick.com, 3cis.biz, livo.co.il and two more.

These name servers tend to co-occur with ns13.digicertdns.net, ns14.digicertdns.net, ns15.digicertdns.net and 7 other name servers in the same DNS delegations.

Host names that have two IP addresses:

ns10.digicertdns.com directs traffic to 208.94.148.159 and 2600:1800::1:1f.

ns11.digicertdns.com directs traffic to 208.80.124.159 and 2600:1801:1::1:1f.

ns12.digicertdns.com directs traffic to 208.80.126.159 and 2600:1802:2::1:1f.

ns13.digicertdns.net directs traffic to 208.80.125.159 and 2600:1801:3::1:1f.

ns14.digicertdns.net directs traffic to 208.80.127.159 and 2600:1802:4::1:1f.

ns15.digicertdns.net directs traffic to 208.94.149.159 and 2600:1800:8::1:1f.

Mail Servers

rmtelegram.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between rmtelegram.com and other domains, including aave-liquidity.com, leon.photos, icubes.in and two others.

These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Host names that have two IP addresses:

aspmx.l.google.com directs traffic to 142.251.16.26 and 2607:f8b0:4004:c21::1a.

alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.