informedaction.com - dns.ninja
informedaction.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.eftydns.com ⭐ | ||||||
| A | 87.253.137.197🇳🇱 TRANSIP-AS87.253.128.0/19 TransIP BV Amsterdam, The Netherlands | ||||||
| PTR | 87-253-137-197.colo.transip.net | ||||||
| NS | ns2.eftydns.com | ||||||
| A | 136.144.254.183🇳🇱 TRANSIP-AS136.144.128.0/17 TransIP BV Amsterdam, The Netherlands | ||||||
| PTR | 136-144-254-183.colo.transip.net | ||||||
| NS | this-domain.name-is-for-sale.com ⚠️ Not in zone NS records | ||||||
| SOA | ns1.eftydns.comhostmaster@informedaction.com 2026-08-13 #1 | ||||||
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=1786874439 | ||||||
Previously MX for
informedaction.com |
Same first word
informedaction.com |
informedaction.ca |
Similar names
DNS History
15 records (3 active, 12 former)
●NSns1.eftydns.com2026-03-13 → 2026-08-16 · 3 obs
○ 2017-05-24 11:55:36
● 2026-03-13 23:59:26
● 2026-08-16 10:16:26
● 2026-03-13 23:59:26
● 2026-08-16 10:16:26
○NSns1.slowinter.net2015-06-04 → 2015-11-01 · 4 obs
● 2015-06-04 02:30:28
● 2015-11-01 15:50:28
○ 2016-01-19 05:22:08
○ 2026-08-16 10:16:26
● 2015-11-01 15:50:28
○ 2016-01-19 05:22:08
○ 2026-08-16 10:16:26
○NSns1.supportedns.com2016-01-19 → 2017-05-24 · 5 obs
○ 2015-11-01 15:50:28
● 2016-01-19 05:22:08
● 2017-05-24 11:55:36
○ 2026-03-13 23:59:26
○ 2026-08-16 10:16:26
● 2016-01-19 05:22:08
● 2017-05-24 11:55:36
○ 2026-03-13 23:59:26
○ 2026-08-16 10:16:26
●NSns2.eftydns.com2026-03-13 → 2026-08-16 · 3 obs
○ 2017-05-24 11:55:36
● 2026-03-13 23:59:26
● 2026-08-16 10:16:26
● 2026-03-13 23:59:26
● 2026-08-16 10:16:26
○NSns2.slowinter.net2015-06-04 → 2015-11-01 · 4 obs
● 2015-06-04 02:30:28
● 2015-11-01 15:50:28
○ 2016-01-19 05:22:08
○ 2026-08-16 10:16:26
● 2015-11-01 15:50:28
○ 2016-01-19 05:22:08
○ 2026-08-16 10:16:26
○NSns2.supportedns.com2016-01-19 → 2017-05-24 · 5 obs
○ 2015-11-01 15:50:28
● 2016-01-19 05:22:08
● 2017-05-24 11:55:36
○ 2026-03-13 23:59:26
○ 2026-08-16 10:16:26
● 2016-01-19 05:22:08
● 2017-05-24 11:55:36
○ 2026-03-13 23:59:26
○ 2026-08-16 10:16:26
○NSns3.slowinter.net2015-06-04 → 2015-11-01 · 4 obs
● 2015-06-04 02:30:28
● 2015-11-01 15:50:28
○ 2016-01-19 05:22:08
○ 2026-08-16 10:16:26
● 2015-11-01 15:50:28
○ 2016-01-19 05:22:08
○ 2026-08-16 10:16:26
○NSns3.supportedns.com2016-04-14 → 2017-05-24 · 5 obs
○ 2016-01-19 05:22:08
● 2016-04-14 09:57:54
● 2017-05-24 11:55:36
○ 2026-03-13 23:59:26
○ 2026-08-16 10:16:26
● 2016-04-14 09:57:54
● 2017-05-24 11:55:36
○ 2026-03-13 23:59:26
○ 2026-08-16 10:16:26
●NSthis-domain.name-is-for-sale.com2026-03-13 → 2026-08-16 · 3 obs
○ 2017-05-24 11:55:36
● 2026-03-13 23:59:26
● 2026-08-16 10:16:26
● 2026-03-13 23:59:26
● 2026-08-16 10:16:26
○MXinformedaction.com2015-06-04 → 2016-01-19 · 4 obs
● 2015-06-04 02:30:28
● 2016-01-19 05:22:08
○ 2016-04-14 09:57:54
○ 2026-08-16 10:16:26
● 2016-01-19 05:22:08
○ 2016-04-14 09:57:54
○ 2026-08-16 10:16:26
○MXscanner01.mail.supportedns.com2016-04-14 → 2017-05-24 · 5 obs
○ 2016-01-19 05:22:08
● 2016-04-14 09:57:54
● 2017-05-24 11:55:36
○ 2026-03-13 23:59:26
○ 2026-08-16 10:16:26
● 2016-04-14 09:57:54
● 2017-05-24 11:55:36
○ 2026-03-13 23:59:26
○ 2026-08-16 10:16:26
○MXscanner02.mail.supportedns.com2016-04-14 → 2017-05-24 · 5 obs
○ 2016-01-19 05:22:08
● 2016-04-14 09:57:54
● 2017-05-24 11:55:36
○ 2026-03-13 23:59:26
○ 2026-08-16 10:16:26
● 2016-04-14 09:57:54
● 2017-05-24 11:55:36
○ 2026-03-13 23:59:26
○ 2026-08-16 10:16:26
○A162.244.253.1172016-01-19 → 2017-05-24 · 5 obs
○ 2015-11-01 15:50:28
● 2016-01-19 05:22:08
● 2017-05-24 11:55:36
○ 2026-03-13 23:59:26
○ 2026-08-16 10:16:26
● 2016-01-19 05:22:08
● 2017-05-24 11:55:36
○ 2026-03-13 23:59:26
○ 2026-08-16 10:16:26
○A162.244.253.602015-06-04 → 2015-11-01 · 4 obs
● 2015-06-04 02:30:28
● 2015-11-01 15:50:28
○ 2016-01-19 05:22:08
○ 2026-08-16 10:16:26
● 2015-11-01 15:50:28
○ 2016-01-19 05:22:08
○ 2026-08-16 10:16:26
○A86.105.245.692026-03-13 → 2026-07-13 · 9 obs
○ 2017-05-24 11:55:36
● 2026-03-13 23:59:26
● 2026-05-14 16:04:08
○ 2026-05-18 07:15:58
● 2026-06-22 15:07:20
○ 2026-06-27 06:12:24
● 2026-07-13 05:47:26
○ 2026-07-14 22:36:30
○ 2026-08-16 10:16:26
● 2026-03-13 23:59:26
● 2026-05-14 16:04:08
○ 2026-05-18 07:15:58
● 2026-06-22 15:07:20
○ 2026-06-27 06:12:24
● 2026-07-13 05:47:26
○ 2026-07-14 22:36:30
○ 2026-08-16 10:16:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| informedaction.com | ns1.eftydns.com, ns2.eftydns.com, this-domain.name-is-for-sale.com | 3 records |
✅ Authoritative Response
Server:87.253.137.197
NS records: ns1.eftydns.com, ns2.eftydns.com, this-domain.name-is-for-sale.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for informedaction.com (unsigned zone)
⏱️ Timing
Total: 1625ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 86.105.245.69 |
| NS | 2 | ns1.eftydns.com, ns2.eftydns.com |
| SOA | 1 | ns1.eftydns.com hostmaster.informedactio |
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns1.eftydns.com, ns2.eftydns.com, this-domain.name-is-for-sale.com)
Analysis
Name Servers
DNS for informedaction.com is handled by three authoritative name servers: ns1.eftydns.com, ns2.eftydns.com and this-domain.name-is-for-sale.com.
informedaction.com has at least partial name server overlap with other domains, such as teal.com, axalx.com, koogio.com and two others.
It is common to see these name servers used together with name servers dns1.a.io and dns2.a.io.
ns1.eftydns.com directs to 87.253.137.197 and ns2.eftydns.com directs to 136.144.254.183; each host name points to exactly one IP number.