leadmessage.com - dns.ninja
leadmessage.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 107.20.99.174🇺🇸 Amazon107.20.0.0/16 EC2 Prefix | ||||||
| PTR | ec2-107-20-99-174.compute-1.amazonaws.com | ||||||
| NS | ns1.wpgamahost7.com ⭐ | ||||||
| A | 52.7.25.249🇺🇸 Amazon52.4.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-7-25-249.compute-1.amazonaws.com | ||||||
| NS | ns2.wpgamahost7.com | ||||||
| A | 52.70.250.102🇺🇸 Amazon52.70.0.0/15 EC2 IAD prefix | ||||||
| PTR | ec2-52-70-250-102.compute-1.amazonaws.com | ||||||
| MX | leadmessage.com ⭐ | ||||||
| A | 107.20.99.174🇺🇸 Amazon107.20.0.0/16 EC2 Prefix | ||||||
| PTR | ec2-107-20-99-174.compute-1.amazonaws.com | ||||||
| TXT | amazonses:AWZA1Gc9s644p2SHephMBjPjBZc9DrZ20UlOtB8G5Z4= | ||||||
| TXT | v=spf1 +a +mx +ip4:3.220.200.51 +ip4:107.20.99.174 +include:_spf.rmkta.com +i... | ||||||
| SOA | ns1.wpgamahost7.comsupport@wpgateway.com 2025-03-31 #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.netnstld@verisign-grs.com serial=1791759439 | ||||||
MX for
leadmessage.com |
Same first word
Similar names
sealedgames.co.uk |
sealedgames.blog |
messagedeal.com |
dealmessage.com |
mesadegales.com |
messagelead.com |
sealedgames.com |
Previous names
Next names
DNS History
18 records (4 active, 14 former)
○NSdns1.registrar-servers.com2017-08-18 → 2017-08-18 · 4 obs
● 2017-08-18 05:12:54
○ 2026-09-19 21:30:58
○ 2026-10-11 23:01:22
○NSdns2.registrar-servers.com2017-08-18 → 2017-08-18 · 4 obs
● 2017-08-18 05:12:54
○ 2026-09-19 21:30:58
○ 2026-10-11 23:01:22
●NSns1.wpgamahost7.com2026-09-19 → 2026-10-11 · 3 obs
● 2026-09-19 21:30:58
● 2026-10-11 23:01:22
●NSns2.wpgamahost7.com2026-09-19 → 2026-10-11 · 3 obs
● 2026-09-19 21:30:58
● 2026-10-11 23:01:22
○NSns51.1and1.com2015-06-07 → 2015-10-23 · 4 obs
● 2015-10-23 03:43:24
○ 2016-09-14 04:10:08
○ 2026-10-11 23:01:22
○NSns52.1and1.com2015-06-07 → 2015-10-23 · 4 obs
● 2015-10-23 03:43:24
○ 2016-09-14 04:10:08
○ 2026-10-11 23:01:22
○MXeforward1.registrar-servers.com2017-08-18 → 2017-08-18 · 4 obs
● 2017-08-18 05:12:54
○ 2026-09-19 21:30:58
○ 2026-10-11 23:01:22
○MXeforward2.registrar-servers.com2017-08-18 → 2017-08-18 · 4 obs
● 2017-08-18 05:12:54
○ 2026-09-19 21:30:58
○ 2026-10-11 23:01:22
○MXeforward3.registrar-servers.com2017-08-18 → 2017-08-18 · 4 obs
● 2017-08-18 05:12:54
○ 2026-09-19 21:30:58
○ 2026-10-11 23:01:22
○MXeforward4.registrar-servers.com2017-08-18 → 2017-08-18 · 4 obs
● 2017-08-18 05:12:54
○ 2026-09-19 21:30:58
○ 2026-10-11 23:01:22
○MXeforward5.registrar-servers.com2017-08-18 → 2017-08-18 · 4 obs
● 2017-08-18 05:12:54
○ 2026-09-19 21:30:58
○ 2026-10-11 23:01:22
●MXleadmessage.com2026-09-19 → 2026-10-11 · 3 obs
● 2026-09-19 21:30:58
● 2026-10-11 23:01:22
○MXmx00.1and1.com2015-06-07 → 2015-10-23 · 4 obs
● 2015-10-23 03:43:24
○ 2016-09-14 04:10:08
○ 2026-10-11 23:01:22
○MXmx01.1and1.com2015-06-07 → 2015-10-23 · 4 obs
● 2015-10-23 03:43:24
○ 2016-09-14 04:10:08
○ 2026-10-11 23:01:22
●A107.20.99.1742026-09-19 → 2026-10-11 · 3 obs
● 2026-09-19 21:30:58
● 2026-10-11 23:01:22
○A162.255.119.1822017-08-18 → 2017-08-18 · 4 obs
● 2017-08-18 05:12:54
○ 2026-09-19 21:30:58
○ 2026-10-11 23:01:22
○A198.251.70.472015-06-07 → 2015-10-23 · 4 obs
● 2015-10-23 03:43:24
○ 2016-09-14 04:10:08
○ 2026-10-11 23:01:22
○A2607:f1c0:1000:203d:5708:b7c0:483c:68092015-06-07 → 2015-10-23 · 4 obs
● 2015-10-23 03:43:24
○ 2016-09-14 04:10:08
○ 2026-10-11 23:01:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, c.gtld-servers.net, m.gtld-servers.net, b.gtld-servers.net... | - |
| leadmessage.com | ns2.wpgamahost7.com, ns1.wpgamahost7.com | 2 records |
✅ Authoritative Response
Server:52.7.25.249
NS records: ns2.wpgamahost7.com, ns1.wpgamahost7.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadmessage.com (unsigned zone)
⏱️ Timing
Total: 291ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 107.20.99.174 |
| NS | 2 | ns2.wpgamahost7.com, ns1.wpgamahost7.com |
| MX | 1 | leadmessage.com (pri: 0) |
| TXT | 2 | amazonses:AWZA1Gc9s644p2SHephMBjPjBZc9Dr, v=spf1 +a +mx +ip4:3.220.200.51 +ip4:107 |
| SOA | 1 | ns1.wpgamahost7.com support.wpgateway.co |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns2.wpgamahost7.com, ns1.wpgamahost7.com)
Analysis
Mail Server Role
leadmessage.com acts as its own mail server.
IP Addresses
leadmessage.com points to a single IP number: 107.20.99.174.
Additional host names — jvjack.com, mycallmessage.com, wpgateway.com and two others — share IP numbers with leadmessage.com.
Name Servers
leadmessage.com is delegated to two name servers: ns1.wpgamahost7.com and ns2.wpgamahost7.com.
leadmessage.com shares its name server setup with other domains, including mycallmessage.com, wpgateway.com, jackhopman.com and two others.
ns1.wpgamahost7.com → 52.7.25.249 and ns2.wpgamahost7.com → 52.70.250.102: one IP number per host name.
Mail Servers
leadmessage.com has a single mail server: leadmessage.com itself.
leadmessage.com resolves to a single IP number: 107.20.99.174.