snapaction.com - dns.ninja
snapaction.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=1786097834 | ||||||
Same first word
snapaction.com |
snapaction.com.au |
snapaction.net |
Similar names
DNS History
12 records (9 active, 3 former)
●NSns1.systemdns.com2020-01-21 → 2026-08-07 · 3 obs
● 2020-01-21 17:05:14
● 2026-08-07 10:19:48
●NSns2.systemdns.com2020-01-21 → 2026-08-07 · 3 obs
● 2020-01-21 17:05:14
● 2026-08-07 10:19:48
●NSns3.systemdns.com2020-01-21 → 2026-08-07 · 3 obs
● 2020-01-21 17:05:14
● 2026-08-07 10:19:48
○NSparking1.mdnsservice.com2015-07-04 → 2017-01-30 · 4 obs
● 2017-01-30 09:41:42
○ 2020-01-21 17:05:14
○ 2026-08-07 10:19:48
○NSparking2.mdnsservice.com2015-07-04 → 2017-01-30 · 4 obs
● 2017-01-30 09:41:42
○ 2020-01-21 17:05:14
○ 2026-08-07 10:19:48
●MXalt1.aspmx.l.google.com2026-03-28 → 2026-08-07 · 2 obs
● 2026-08-07 10:19:48
●MXalt2.aspmx.l.google.com2026-03-28 → 2026-08-07 · 2 obs
● 2026-08-07 10:19:48
●MXaspmx.l.google.com2026-03-28 → 2026-08-07 · 2 obs
● 2026-08-07 10:19:48
●MXaspmx2.googlemail.com2026-03-28 → 2026-08-07 · 2 obs
● 2026-08-07 10:19:48
●MXaspmx3.googlemail.com2026-03-28 → 2026-08-07 · 2 obs
● 2026-08-07 10:19:48
○A208.91.197.1602015-07-04 → 2017-01-30 · 4 obs
● 2017-01-30 09:41:42
○ 2020-01-21 17:05:14
○ 2026-08-07 10:19:48
●A64.99.64.372026-03-28 → 2026-08-07 · 3 obs
● 2026-03-28 10:45:50
● 2026-08-07 10:19:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net, e.gtld-servers.net... | - |
| snapaction.com | ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com | 6 records |
✅ Authoritative Response
Server:64.99.96.36
NS records: ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for snapaction.com (unsigned zone)
⏱️ Timing
Total: 334ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 64.99.64.37 |
| NS | 3 | ns3.systemdns.com, ns1.systemdns.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 20), aspmx3.googlemail.com (pri: 30)... |
| SOA | 1 | ns1.systemdns.com hostmaster.systemdns.c |
📌 Glue Records Collected
Total: 6
Out-of-bailiwick: 6 (ns1.systemdns.com, ns1.systemdns.com, ns2.systemdns.com...)
Analysis
IP Addresses
snapaction.com resolves to just one IP address, 64.99.64.37.
Two other host names, along with exchange.velocityprogram.com, canpom.com and pointbroker.net, also share IP numbers with snapaction.com.
Name Servers
The authoritative name servers for snapaction.com are ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com — three in total.
snapaction.com has at least partial name server overlap with other domains, such as betsyskrip.com, steeleheightscommunity.com, amcooling.com and two others.
ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com all resolve to exactly two IP numbers apiece: ns1.systemdns.com → 216.40.47.90 and 2604:4000:0:d:216:40:47:90; ns2.systemdns.com → 64.98.148.16 and 2604:4000:2800:d:64:99:148:16; ns3.systemdns.com → 64.99.96.36 and 2604:4000:0:d:64:99:96:36.
Mail Servers
snapaction.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between snapaction.com and other domains, including jaikvin.com, notar-vizireanu.ro, imw.com and two others.
These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 192.178.155.27 and 2607:f8b0:4004:c23::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.