reactcm.com - dns.ninja
reactcm.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=1784772252 | ||||||
Same first word
reactcm.com |
Similar names
DNS History
13 records (8 active, 5 former)
●NSdns1.registrar-servers.com2026-03-26 → 2026-07-23 · 3 obs
● 2026-03-26 08:55:14
● 2026-07-23 02:19:52
●NSdns2.registrar-servers.com2026-03-26 → 2026-07-23 · 3 obs
● 2026-03-26 08:55:14
● 2026-07-23 02:19:52
○NSns8329.hostgator.com2017-05-11 → 2017-05-11 · 3 obs
○ 2026-03-26 08:55:14
○ 2026-07-23 02:19:52
○NSns8330.hostgator.com2017-05-11 → 2017-05-11 · 3 obs
○ 2026-03-26 08:55:14
○ 2026-07-23 02:19:52
●MXalt1.aspmx.l.google.com2017-05-11 → 2026-07-23 · 2 obs
● 2026-07-23 02:19:52
●MXalt2.aspmx.l.google.com2017-05-11 → 2026-07-23 · 2 obs
● 2026-07-23 02:19:52
○MXalt3.aspmx.l.google.com2017-05-11 → 2017-05-11 · 3 obs
○ 2026-03-26 08:55:14
○ 2026-07-23 02:19:52
○MXalt4.aspmx.l.google.com2017-05-11 → 2017-05-11 · 3 obs
○ 2026-03-26 08:55:14
○ 2026-07-23 02:19:52
●MXaspmx.l.google.com2017-05-11 → 2026-07-23 · 2 obs
● 2026-07-23 02:19:52
●MXaspmx2.googlemail.com2026-03-26 → 2026-07-23 · 3 obs
● 2026-03-26 08:55:14
● 2026-07-23 02:19:52
●MXaspmx3.googlemail.com2026-03-26 → 2026-07-23 · 3 obs
● 2026-03-26 08:55:14
● 2026-07-23 02:19:52
○A108.167.140.882017-05-11 → 2017-05-11 · 3 obs
○ 2026-03-26 08:55:14
○ 2026-07-23 02:19:52
●A35.188.40.1212026-03-26 → 2026-07-23 · 3 obs
● 2026-03-26 08:55:14
● 2026-07-23 02:19:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| reactcm.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.132.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for reactcm.com (unsigned zone)
⏱️ Timing
Total: 335ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 35.188.40.121 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
IP Addresses
reactcm.com resolves to just one IP address, 35.188.40.121.
Two other host names, along with pointblue.org, eric-english.com and flaxandtwine.wpengine.com, also share IP numbers with reactcm.com.
Name Servers
reactcm.com is delegated to two name servers: dns1.registrar-servers.com and dns2.registrar-servers.com.
reactcm.com shares its NS records with other domains, for example avmadesimple.com, pieoneone.com, collective-systems.com and two others.
reactcm.com has overlapping name servers with several other domains — among them bestrntobsn.net, metavod.com, hollyspringshouses.com and keyimg.com.
The name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com are commonly seen alongside these name servers.
dns1.registrar-servers.com and dns2.registrar-servers.com each resolve to two IP addresses: dns1.registrar-servers.com points to 156.154.132.200 and 2610:a1:1024::200, while dns2.registrar-servers.com points to 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
Five mail servers handle reactcm.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between reactcm.com and other domains, including ns500734.ns500699.ns500734.ns500693.ns500734.ns500699.ns500699.ns500693.ns500693.ns500699.ns500588.ns500693.ns500602.dtrkdll.com, ns500759.ns500698.ns500759.ns500735.ns500736.ns500736.ns500735.ns500736.ns500736.ns500708.ns500708.ns500576.ns500576.ns500576.ns500652.trackreceptor.com, ns500765.ns500693.ns500734.ns500699.ns500693.ns500693.ns500693.ns500588.ns500632.ns500632.ns500578.ns500110.dtrkdll.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com points to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com points to 172.253.122.26 and 2607:f8b0:4004:c23::1a.
alt1.aspmx.l.google.com points to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com points to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx2.googlemail.com and alt1.aspmx.l.google.com are host names that each point to 2800:3f0:4003:c0f::1a IP addresses.
aspmx3.googlemail.com and alt2.aspmx.l.google.com are host names that each point to 172.253.116.27 IP addresses.