letmereach.com - dns.ninja

`letmereach.com`

DNSSEC	⚠️ Not signed
A	67.227.199.102^{🇺🇸 LiquidWeb67.227.128.0/17 Liquidweb LLC}
NS	`ns1.rchsolutionsinc.com` ⭐
		A	67.227.199.102^{🇺🇸 LiquidWeb67.227.128.0/17 Liquidweb LLC}
NS	`ns2.rchsolutionsinc.com`
		A	67.227.219.209^{🇺🇸 LiquidWeb67.227.128.0/17 Liquidweb LLC}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c17::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f27.1e100.net`
		A	142.251.163.26^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.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::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 +a +mx +ip4:67.227.199.102 include:_spf.google.com ~all`
SOA	`ns1.rchsolutionsinc.com`devnull@sourcedns.com 2026-06-27 #1

`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=1785699307

WOT: SAFE (86/100)

Same first word

letmereach.com

Similar names

DNS History

18 records (8 active, 10 former)

●NSns1.rchsolutionsinc.com2016-08-05 → 2026-08-02 · 3 obs

○ 2016-03-28 14:24:26
● 2016-08-05 17:29:52
● 2026-08-02 19:44:22

○NSns1.wordpress.com2015-05-21 → 2016-03-28 · 4 obs

● 2015-05-21 21:28:20
● 2016-03-28 14:24:26
○ 2016-08-05 17:29:52
○ 2026-08-02 19:44:22

●NSns2.rchsolutionsinc.com2016-08-05 → 2026-08-02 · 3 obs

○ 2016-03-28 14:24:26
● 2016-08-05 17:29:52
● 2026-08-02 19:44:22

○NSns2.wordpress.com2015-05-21 → 2016-03-28 · 4 obs

● 2015-05-21 21:28:20
● 2016-03-28 14:24:26
○ 2016-08-05 17:29:52
○ 2026-08-02 19:44:22

○NSns3.wordpress.com2015-05-21 → 2016-03-28 · 4 obs

● 2015-05-21 21:28:20
● 2016-03-28 14:24:26
○ 2016-08-05 17:29:52
○ 2026-08-02 19:44:22

●MXalt1.aspmx.l.google.com2016-10-10 → 2026-08-02 · 3 obs

○ 2016-08-13 12:00:04
● 2016-10-10 19:07:58
● 2026-08-02 19:44:22

●MXalt2.aspmx.l.google.com2016-10-10 → 2026-08-02 · 3 obs

○ 2016-08-13 12:00:04
● 2016-10-10 19:07:58
● 2026-08-02 19:44:22

●MXalt3.aspmx.l.google.com2016-10-10 → 2026-08-02 · 3 obs

○ 2016-08-13 12:00:04
● 2016-10-10 19:07:58
● 2026-08-02 19:44:22

●MXalt4.aspmx.l.google.com2016-10-10 → 2026-08-02 · 3 obs

○ 2016-08-13 12:00:04
● 2016-10-10 19:07:58
● 2026-08-02 19:44:22

●MXaspmx.l.google.com2016-10-10 → 2026-08-02 · 3 obs

○ 2016-08-13 12:00:04
● 2016-10-10 19:07:58
● 2026-08-02 19:44:22

○MXmx.zoho.com2016-08-05 → 2016-08-13 · 5 obs

○ 2016-03-28 14:24:26
● 2016-08-05 17:29:52
● 2016-08-13 12:00:04
○ 2016-10-10 19:07:58
○ 2026-08-02 19:44:22

○MXmx.zohomail.com2015-05-21 → 2016-03-28 · 4 obs

● 2015-05-21 21:28:20
● 2016-03-28 14:24:26
○ 2016-08-05 17:29:52
○ 2026-08-02 19:44:22

○MXmx2.zoho.com2016-08-05 → 2016-08-13 · 5 obs

○ 2016-03-28 14:24:26
● 2016-08-05 17:29:52
● 2016-08-13 12:00:04
○ 2016-10-10 19:07:58
○ 2026-08-02 19:44:22

○MXmx2.zohomail.com2015-05-21 → 2016-03-28 · 4 obs

● 2015-05-21 21:28:20
● 2016-03-28 14:24:26
○ 2016-08-05 17:29:52
○ 2026-08-02 19:44:22

○MXmx3.zoho.com2016-08-05 → 2016-08-13 · 5 obs

○ 2016-03-28 14:24:26
● 2016-08-05 17:29:52
● 2016-08-13 12:00:04
○ 2016-10-10 19:07:58
○ 2026-08-02 19:44:22

○A192.0.78.242015-05-21 → 2016-03-28 · 4 obs

● 2015-05-21 21:28:20
● 2016-03-28 14:24:26
○ 2016-08-05 17:29:52
○ 2026-08-02 19:44:22

○A192.0.78.252015-05-21 → 2016-03-28 · 4 obs

● 2015-05-21 21:28:20
● 2016-03-28 14:24:26
○ 2016-08-05 17:29:52
○ 2026-08-02 19:44:22

●A67.227.199.1022016-08-05 → 2026-08-02 · 3 obs

○ 2016-03-28 14:24:26
● 2016-08-05 17:29:52
● 2026-08-02 19:44:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
letmereach.com	ns1.rchsolutionsinc.com, ns2.rchsolutionsinc.com	2 records

✅ Authoritative Response

Server:67.227.219.209

NS records: ns1.rchsolutionsinc.com, ns2.rchsolutionsinc.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for letmereach.com (unsigned zone)

⏱️ Timing

Total: 186ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`67.227.199.102`
NS	2	`ns1.rchsolutionsinc.com, ns2.rchsolutionsinc.com`
MX	5	`alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 +a +mx +ip4:67.227.199.102 includ`
SOA	1	`ns1.rchsolutionsinc.com devnull.sourcedn`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.rchsolutionsinc.com, ns2.rchsolutionsinc.com)

Analysis

IP Addresses

letmereach.com resolves to just one IP address, 67.227.199.102.

Two other host names, along with aspendancingfountain.com, _dc-mx.fddfe0e2bea4.kirkfish.com and southernsanitationinc.net, also share IP numbers with letmereach.com.

Name Servers

letmereach.com has two authoritative name servers — ns1.rchsolutionsinc.com and ns2.rchsolutionsinc.com.

letmereach.com shares its NS records with other domains, for example aspendancingfountain.com, southernsanitationinc.net, collierfair.com and two others.

ns1.rchsolutionsinc.com → 67.227.199.102 and ns2.rchsolutionsinc.com → 67.227.219.209: one IP number per host name.

Mail Servers

letmereach.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 letmereach.com and other domains, including ns500768.ns500759.ns500758.ns500758.ns500735.ns500735.ns500735.ns500736.ns500735.ns500708.ns500708.ns500708.ns500576.ns500686.ns500619.trackreceptor.com, ns500699.ns500699.ns500734.ns500693.ns500699.ns500588.ns500588.ns500588.ns500693.ns500699.ns500693.ns500588.ns500632.ns500612.ns500612.ns500110.dtrkdll.com, ns500759.ns500759.ns500698.ns500736.ns500735.ns500735.ns500735.ns500735.ns500576.ns500708.ns500708.ns500698.ns500576.ns500619.ns500619.trackreceptor.com 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 resolves to 142.251.163.26 and 2607:f8b0:4004:c17::1b.

alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1b.

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

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

alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.