ferroprotocol.com - dns.ninja
ferroprotocol.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=1784911802 | ||||||
Same first word
ferroprotocol.com |
DNS History
11 records (11 active, 0 former)
●NSemma.ns.cloudflare.com2026-02-20 → 2026-07-24 · 2 obs
● 2026-07-24 17:16:14
●NSotto.ns.cloudflare.com2026-02-20 → 2026-07-24 · 2 obs
● 2026-07-24 17:16:14
●MXalt1.aspmx.l.google.com2026-02-20 → 2026-07-24 · 2 obs
● 2026-07-24 17:16:14
●MXalt2.aspmx.l.google.com2026-02-20 → 2026-07-24 · 2 obs
● 2026-07-24 17:16:14
●MXalt3.aspmx.l.google.com2026-02-20 → 2026-07-24 · 2 obs
● 2026-07-24 17:16:14
●MXalt4.aspmx.l.google.com2026-02-20 → 2026-07-24 · 2 obs
● 2026-07-24 17:16:14
●MXaspmx.l.google.com2026-02-20 → 2026-07-24 · 2 obs
● 2026-07-24 17:16:14
●A104.20.43.322026-02-20 → 2026-07-24 · 2 obs
● 2026-07-24 17:16:14
●A172.66.156.422026-02-20 → 2026-07-24 · 2 obs
● 2026-07-24 17:16:14
●A2606:4700:10::6814:2b202026-02-20 → 2026-07-24 · 2 obs
● 2026-07-24 17:16:14
●A2606:4700:10::ac42:9c2a2026-02-20 → 2026-07-24 · 2 obs
● 2026-07-24 17:16:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, e.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net... | - |
| ferroprotocol.com | emma.ns.cloudflare.com, otto.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.192.112
NS records: emma.ns.cloudflare.com, otto.ns.cloudflare.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 709ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 172.66.156.42, 104.20.43.32 |
| AAAA | 2 | 2606:4700:10::6814:2b20, 2606:4700:10::ac42:9c2a |
| NS | 2 | emma.ns.cloudflare.com, otto.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 3 | google-site-verification=Iww7gzNlWfBjZSY, google-site-verification=v2MZ_EnLW1hDzwV... |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h2"] |
| SOA | 1 | emma.ns.cloudflare.com dns.cloudflare.co |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (emma.ns.cloudflare.com, emma.ns.cloudflare.com, emma.ns.cloudflare.com...)
Analysis
IP Addresses
ferroprotocol.com directs to four IP numbers, which are 104.20.43.32, 172.66.156.42, 2606:4700:10::6814:2b20 and 2606:4700:10::ac42:9c2a.
laerd.com, post.herdt.com.cdn.cloudflare.net, cms.herdt.com.cdn.cloudflare.net and two other host names share IP numbers with ferroprotocol.com.
Name Servers
ferroprotocol.com uses two name servers for its delegation: emma.ns.cloudflare.com and otto.ns.cloudflare.com.
ferroprotocol.com uses the same name servers as several other domains — among them mx.kh.ua, ballz.fun, countrymanstorage.co.uk and two more.
There is at least partial name server overlap between ferroprotocol.com and other domains — jmqfw.com, sphynxsoft.com, funkbrasil.com and two more among them.
These name servers frequently co-occur with the name servers lilyana.ns.cloudflare.com and brad.ns.cloudflare.com.
Hostnames that resolve to 6 IP addresses:
Hostname emma.ns.cloudflare.com directs to 108.162.192.112, 172.64.32.112 and 173.245.58.112 along with 3 other IP addresses.
Hostname otto.ns.cloudflare.com directs to 108.162.195.135, 162.159.44.135 and 172.64.35.135 along with 3 other IP addresses.
Mail Servers
Five mail servers handle ferroprotocol.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
ferroprotocol.com has at least partial mail server overlap with other domains such as mikenas.com, ns500734.ns500693.ns500734.ns500693.ns500699.ns500699.ns500734.ns500588.ns500699.ns500632.ns500588.ns500588.ns500632.ns500588.ns500588.ns500588.dtrkdll.com, cinestaanfilmcompany.com and two more.
These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com directs traffic to 64.233.180.27 and 2607:f8b0:4004:c23::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::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1b.