🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`launchlansing.com`

DNSSEC	⚠️ Not signed
A	141.193.213.10^{🇺🇸 CLOUDFLARESPECTRUM141.193.213.0/24 WPEngine, Inc. 504 Lavaca Street, 1000, Austin, TX 78701, US}
A	141.193.213.11^{🇺🇸 CLOUDFLARESPECTRUM141.193.213.0/24 WPEngine, Inc. 504 Lavaca Street, 1000, Austin, TX 78701, US}
NS	`ns1.launchri.com` ⭐
		A	96.30.40.130^{🇺🇸 LiquidWeb96.30.0.0/18 Liquid Web LLC 2703 Ena Dr Lansing, MI 48917}
NS	`ns2.launchri.com`
		A	96.30.40.131^{🇺🇸 LiquidWeb96.30.0.0/18 Liquid Web LLC 2703 Ena Dr Lansing, MI 48917}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c06::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f27.1e100.net`
		A	192.179.18.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ry-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽²⁰⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 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	`aspmx3.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`v=spf1 a mx include:_spf.google.com ~all`
SOA	`ns1.launchri.com`support@obxtechsolutions.com 2026-08-21 #0

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

Same first word

launchlansing.com

Previous names

Next names

DNS History

10 records (9 active, 1 former)

●NSns1.launchri.com2017-09-28 → 2026-08-21 · 2 obs

● 2017-09-28 08:30:40
● 2026-08-21 05:36:54

●NSns2.launchri.com2017-09-28 → 2026-08-21 · 2 obs

● 2017-09-28 08:30:40
● 2026-08-21 05:36:54

●MXalt1.aspmx.l.google.com2017-09-28 → 2026-08-21 · 2 obs

● 2017-09-28 08:30:40
● 2026-08-21 05:36:54

●MXalt2.aspmx.l.google.com2017-09-28 → 2026-08-21 · 2 obs

● 2017-09-28 08:30:40
● 2026-08-21 05:36:54

●MXaspmx.l.google.com2017-09-28 → 2026-08-21 · 2 obs

● 2017-09-28 08:30:40
● 2026-08-21 05:36:54

●MXaspmx2.googlemail.com2017-09-28 → 2026-08-21 · 2 obs

● 2017-09-28 08:30:40
● 2026-08-21 05:36:54

●MXaspmx3.googlemail.com2017-09-28 → 2026-08-21 · 2 obs

● 2017-09-28 08:30:40
● 2026-08-21 05:36:54

●A141.193.213.102026-08-21 → 2026-08-21 · 3 obs

○ 2017-09-28 08:30:40
● 2026-08-21 03:09:50
● 2026-08-21 05:36:54

●A141.193.213.112026-08-21 → 2026-08-21 · 3 obs

○ 2017-09-28 08:30:40
● 2026-08-21 03:09:50
● 2026-08-21 05:36:54

○A96.30.40.1312017-09-28 → 2017-09-28 · 3 obs

● 2017-09-28 08:30:40
○ 2026-08-21 03:09:50
○ 2026-08-21 05:36:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net...	-
launchlansing.com	ns1.launchri.com, ns2.launchri.com	2 records

✅ Authoritative Response

Server:96.30.40.130

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for launchlansing.com (unsigned zone)

⏱️ Timing

Total: 247ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`141.193.213.11, 141.193.213.10`
NS	2	`ns1.launchri.com, ns2.launchri.com`
MX	5	`alt2.aspmx.l.google.com (pri: 30), aspmx2.googlemail.com (pri: 20)...`
TXT	1	`v=spf1 a mx include:_spf.google.com ~all`
SOA	1	`ns1.launchri.com support.obxtechsolution`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

launchlansing.com has two IP addresses: 141.193.213.10 and 141.193.213.11

jeffersonvineyards.com, www.hudsonandcrane.com, warregohotel.com.au plus two other host names have IP numbers in common with launchlansing.com.

Name Servers

The NS records for launchlansing.com delegate to ns1.launchri.com and ns2.launchri.com.

launchlansing.com has the same NS records as launchasheville.com, launchtrampolinepark.com, launchdoral.com and launchri.com.

Each of ns1.launchri.com and ns2.launchri.com has one IP address: ns1.launchri.com uses 96.30.40.130 and ns2.launchri.com uses 96.30.40.131.

Mail Servers

Five mail servers handle launchlansing.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

At least some of the mail servers used by launchlansing.com are shared with other domains: nearfx.com, yamauchi-tax.jp, brazierillustration.co.uk and two others among them.

These mail servers are often deployed together with alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.

Host names pointing to two IP addresses:

The A records for aspmx2.googlemail.com return 192.178.234.26 and 2800:3f0:4003:c14::1a.

The A records for aspmx3.googlemail.com return 172.253.116.27 and 2a00:1450:400b:c02::1b.

The A records for aspmx.l.google.com return 192.179.18.27 and 2607:f8b0:4004:c06::1b.

The A records for alt1.aspmx.l.google.com return 192.178.234.27 and 2800:3f0:4003:c14::1b.

The A records for alt2.aspmx.l.google.com return 172.253.116.27 and 2a00:1450:400b:c02::1a.

aspmx3.googlemail.com and alt2.aspmx.l.google.com each have 172.253.116.27 IP addresses.