launchmycontent.com - dns.ninja
launchmycontent.com
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.netnstld@verisign-grs.com serial=1782885071 | ||||||
Same first word
launchmycontent.com |
DNS History
9 records (9 active, 0 former)
●NSns03.domaincontrol.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 05:54:22
●NSns04.domaincontrol.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 05:54:22
●MXalt1.aspmx.l.google.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 05:54:22
●MXalt2.aspmx.l.google.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 05:54:22
●MXalt3.aspmx.l.google.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 05:54:22
●MXalt4.aspmx.l.google.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 05:54:22
●MXaspmx.l.google.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 05:54:22
●A100.24.208.972026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 05:54:22
●A35.172.94.12026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 05:54:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, f.gtld-servers.net, e.gtld-servers.net, h.gtld-servers.net... | - |
| launchmycontent.com | ns03.domaincontrol.com, ns04.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.69.2
NS records: ns03.domaincontrol.com, ns04.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for launchmycontent.com (unsigned zone)
⏱️ Timing
Total: 1160ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 100.24.208.97, 35.172.94.1 |
| NS | 2 | ns03.domaincontrol.com, ns04.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=yqD_LnCc1rO28dg, v=spf1 include:dc-aa8e722993._spfm.launc |
| SOA | 1 | ns03.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns03.domaincontrol.com, ns03.domaincontrol.com, ns04.domaincontrol.com...)
Analysis
IP Addresses
launchmycontent.com resolves to the IP addresses 35.172.94.1 and 100.24.208.97
gruasbermag.com.mx, fmonks.com, intownautocare.net and two other host names share IP numbers with launchmycontent.com.
Name Servers
launchmycontent.com is delegated to two name servers: ns03.domaincontrol.com and ns04.domaincontrol.com.
launchmycontent.com uses the same name servers as several other domains — among them biograde.com, ellwoodatfield.com, digital83.com and two more.
ns03.domaincontrol.com and ns04.domaincontrol.com each resolve to two IP addresses: ns03.domaincontrol.com points to 97.74.101.2 and 2603:5:2150::2, while ns04.domaincontrol.com points to 173.201.69.2 and 2603:5:2250::2.
Mail Servers
launchmycontent.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
launchmycontent.com has at least partial mail server overlap with other domains such as ns500794.ns500821.ns500794.ns500841.ns500795.ns500794.ns500795.ns500795.ns500794.ns500795.lustypartnersfinder.com, hausbe.eu, ns500742.ns500671.ns500754.ns500731.ns500742.ns500705.ns500705.ns500671.lusty(0x736c7574)z.com and two more.
These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com points to 142.250.31.26 and 2607:f8b0:4004:c08::1a.
alt1.aspmx.l.google.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com points to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com points to 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com points to 172.253.157.26 and 2a00:1450:400c:c23::1a.