fromafable.com - dns.ninja
fromafable.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=1785539512 | ||||||
Subdomains
www.fromafable.com |
Same first word
fromafable.com |
DNS History
14 records (10 active, 4 former)
●NSns1.wordpress.com2026-03-24 → 2026-07-31 · 3 obs
● 2026-03-24 21:05:56
● 2026-07-31 23:39:32
●NSns2.wordpress.com2026-03-24 → 2026-07-31 · 3 obs
● 2026-03-24 21:05:56
● 2026-07-31 23:39:32
●NSns3.wordpress.com2026-03-24 → 2026-07-31 · 3 obs
● 2026-03-24 21:05:56
● 2026-07-31 23:39:32
○NSns65.domaincontrol.com2016-12-17 → 2019-04-23 · 4 obs
● 2019-04-23 06:21:30
○ 2026-03-24 21:05:56
○ 2026-07-31 23:39:32
○NSns66.domaincontrol.com2016-12-17 → 2019-04-23 · 4 obs
● 2019-04-23 06:21:30
○ 2026-03-24 21:05:56
○ 2026-07-31 23:39:32
●MXalt1.aspmx.l.google.com2016-12-17 → 2026-07-31 · 2 obs
● 2026-07-31 23:39:32
●MXalt2.aspmx.l.google.com2016-12-17 → 2026-07-31 · 2 obs
● 2026-07-31 23:39:32
●MXaspmx.l.google.com2016-12-17 → 2026-07-31 · 2 obs
● 2026-07-31 23:39:32
●MXaspmx2.googlemail.com2016-12-17 → 2026-07-31 · 2 obs
● 2026-07-31 23:39:32
●MXaspmx3.googlemail.com2016-12-17 → 2026-07-31 · 2 obs
● 2026-07-31 23:39:32
●A15.197.148.332026-03-24 → 2026-07-31 · 3 obs
● 2026-03-24 21:05:56
● 2026-07-31 23:39:32
○A192.147.0.1182016-12-17 → 2016-12-17 · 3 obs
○ 2019-04-23 06:21:30
○ 2026-07-31 23:39:32
○A23.227.38.322019-04-23 → 2019-04-23 · 4 obs
● 2019-04-23 06:21:30
○ 2026-03-24 21:05:56
○ 2026-07-31 23:39:32
●A3.33.130.1902026-03-24 → 2026-07-31 · 3 obs
● 2026-03-24 21:05:56
● 2026-07-31 23:39:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| fromafable.com | ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com | 6 records |
✅ Authoritative Response
Server:198.181.117.9
NS records: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fromafable.com (unsigned zone)
⏱️ Timing
Total: 181ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.33.130.190, 15.197.148.33 |
| NS | 3 | ns1.wordpress.com, ns3.wordpress.com... |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), alt1.aspmx.l.google.com (pri: 5)... |
| SOA | 1 | ns1.wordpress.com hostmaster.wordpress.c |
📌 Glue Records Collected
Total: 6
Out-of-bailiwick: 6 (ns1.wordpress.com, ns1.wordpress.com, ns2.wordpress.com...)
Analysis
Hierarchy
fromafable.com serves as the parent of www.fromafable.com.
IP Addresses
fromafable.com resolves to the IP addresses 3.33.130.190 and 15.197.148.33
Two other host names, along with honkytonknashville.com, onskan.com and hyattvoi-guest.com, also share IP numbers with fromafable.com.
Name Servers
The authoritative name servers for fromafable.com are ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com — three in total.
fromafable.com has at least partial name server overlap with other domains, such as copropratique.fr, reinstall.com, workersgolf.com and two others.
ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com all resolve to exactly two IP numbers apiece: ns1.wordpress.com → 198.181.116.9 and 2a04:fa87:ffff::c6b5:7409; ns2.wordpress.com → 198.181.117.9 and 2a04:fa87:ffff::c6b5:7509; ns3.wordpress.com → 192.0.74.9 and 2620:115:c00f::c000:4a09.
Mail Servers
fromafable.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 fromafable.com and other domains, including ns500759.ns500758.ns500698.ns500759.ns500698.ns500736.ns500735.ns500698.ns500736.ns500698.ns500698.ns500708.ns500698.ns500576.ns500576.ns500619.ns500619.trackreceptor.com, ns500699.ns500699.ns500693.ns500734.ns500699.ns500699.ns500693.ns500699.ns500588.ns500699.ns500693.ns500683.ns500693.ns500632.ns500632.ns500632.ns500612.dtrkdll.com, virtualvisioncomputing.net 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 directs traffic to 108.177.123.27 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 172.253.62.27 and 2607:f8b0:4004:c29::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.27 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.