tefarrow.com - dns.ninja
tefarrow.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.digitalocean.com ⭐ ⚠️ Not in zone NS records | ||||||
| A | 2606:4700:52::ac40:34d2🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| A | 172.64.52.210🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| NS | ns2.digitalocean.com ⚠️ Not in zone NS records | ||||||
| A | 2606:4700:5a::ac40:3515🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| A | 172.64.53.21🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| NS | ns3.digitalocean.com ⚠️ Not in zone NS records | ||||||
| A | 2606:4700:52::ac40:31d1🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| A | 172.64.49.209🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| SOA | ns1.digitalocean.comhostmaster@tefarrow.com serial=0 | ||||||
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=1786375549 | ||||||
Previously MX for
tefarrow.com |
Same first word
tefarrow.com |
Similar names
DNS History
9 records (3 active, 6 former)
●NSns1.digitalocean.com2026-03-08 → 2026-08-10 · 3 obs
● 2026-03-08 00:52:46
● 2026-08-10 15:28:10
○NSns1.snhdns.com2015-05-28 → 2017-06-10 · 4 obs
● 2017-06-10 15:24:10
○ 2026-03-08 00:52:46
○ 2026-08-10 15:28:10
●NSns2.digitalocean.com2026-03-08 → 2026-08-10 · 3 obs
● 2026-03-08 00:52:46
● 2026-08-10 15:28:10
○NSns2.snhdns.com2015-05-28 → 2017-06-10 · 4 obs
● 2017-06-10 15:24:10
○ 2026-03-08 00:52:46
○ 2026-08-10 15:28:10
●NSns3.digitalocean.com2026-03-08 → 2026-08-10 · 3 obs
● 2026-03-08 00:52:46
● 2026-08-10 15:28:10
○MXtefarrow.com2015-05-28 → 2017-06-10 · 4 obs
● 2017-06-10 15:24:10
○ 2026-03-08 00:52:46
○ 2026-08-10 15:28:10
○A129.212.177.1762026-03-08 → 2026-05-08 · 4 obs
● 2026-03-08 00:52:46
● 2026-05-08 05:55:58
○ 2026-08-10 15:28:10
○A198.38.77.1832017-06-10 → 2017-06-10 · 4 obs
● 2017-06-10 15:24:10
○ 2026-03-08 00:52:46
○ 2026-08-10 15:28:10
○A208.76.82.1312015-05-28 → 2016-12-04 · 4 obs
● 2016-12-04 04:55:24
○ 2017-06-10 15:24:10
○ 2026-08-10 15:28:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, a.gtld-servers.net, c.gtld-servers.net, f.gtld-servers.net... | - |
| tefarrow.com | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | 3 records |
✅ Authoritative Response
Server:172.64.53.21
NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tefarrow.com (unsigned zone)
⏱️ Timing
Total: 2309ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| SOA | 1 | ns1.digitalocean.com hostmaster.tefarrow |
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)
Analysis
Name Servers
The authoritative name servers for tefarrow.com are ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com — three in total.
There is at least partial name server overlap between tefarrow.com and other domains — mz-css.net, 24.138.174.in-addr.arpa, pedroafonso.net and two more among them.
ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com → 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com → 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com → 172.64.49.209 and 2606:4700:52::ac40:31d1.