triggerly.com - dns.ninja
triggerly.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 67.227.25.164 | ||||||
| NS | ns1.digitalocean.com ⭐ | ||||||
| A | 2606:4700:52::ac40:34d2Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 172.64.52.210 | ||||||
| NS | ns2.digitalocean.com | ||||||
| A | 2606:4700:5a::ac40:3515Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 172.64.53.21Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns3.digitalocean.com | ||||||
| A | 2606:4700:52::ac40:31d1Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 172.64.49.209 | ||||||
| SOA | ns1.digitalocean.comhostmaster@triggerly.com serial=0 | ||||||
com
| DNSSEC | ⚠️ Not signed | ||||||
| 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=1793591171 | ||||||
Same first word
triggerly.pl |
triggerly.online |
triggerly.net |
triggerly.cloud |
triggerly.com |
triggerly.live |
triggerly.co |
triggerly.dev |
triggerly.in |
triggerly.store |
triggerly.fun |
DNS History
8 records (4 active, 4 former)
●NSns1.digitalocean.com2026-10-06 → 2026-11-02 · 3 obs
● 2026-10-06 12:18:08
● 2026-11-02 03:50:46
○NSns1.hostmonster.com2015-07-02 → 2018-12-30 · 4 obs
● 2018-12-30 13:17:38
○ 2026-10-06 12:18:08
○ 2026-11-02 03:50:46
●NSns2.digitalocean.com2026-10-06 → 2026-11-02 · 3 obs
● 2026-10-06 12:18:08
● 2026-11-02 03:50:46
○NSns2.hostmonster.com2015-07-02 → 2018-12-30 · 4 obs
● 2018-12-30 13:17:38
○ 2026-10-06 12:18:08
○ 2026-11-02 03:50:46
●NSns3.digitalocean.com2026-10-06 → 2026-11-02 · 3 obs
● 2026-10-06 12:18:08
● 2026-11-02 03:50:46
○MXmail.triggerly.com2015-07-02 → 2018-12-30 · 4 obs
● 2018-12-30 13:17:38
○ 2026-10-06 12:18:08
○ 2026-11-02 03:50:46
○A173.255.202.1472015-07-02 → 2018-12-30 · 4 obs
● 2018-12-30 13:17:38
○ 2026-10-06 12:18:08
○ 2026-11-02 03:50:46
●A67.227.25.1642026-10-06 → 2026-11-02 · 3 obs
● 2026-10-06 12:18:08
● 2026-11-02 03:50:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, g.gtld-servers.net, k.gtld-servers.net, c.gtld-servers.net... | - |
| triggerly.com | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | 3 records |
✅ Authoritative Response
Server:172.64.49.209
NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for triggerly.com (unsigned zone)
⏱️ Timing
Total: 1367ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 67.227.25.164 |
| NS | 3 | ns2.digitalocean.com, ns3.digitalocean.com... |
| SOA | 1 | ns1.digitalocean.com hostmaster.triggerl |
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)
Analysis
IP Addresses
triggerly.com has exactly one IP address — 67.227.25.164.
Name Servers
Three name servers are authoritative for triggerly.com: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.
ns1.digitalocean.com resolves to 172.64.52.210 and 2606:4700:52::ac40:34d2. ns2.digitalocean.com resolves to 172.64.53.21 and 2606:4700:5a::ac40:3515. ns3.digitalocean.com resolves to 172.64.49.209 and 2606:4700:52::ac40:31d1. All three hostnames point to two IP numbers each.