securitycogs.com - robtex.com
securitycogs.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=1788467585 | ||||||
Same first word
securitycogs.com |
Previous names
Next names
DNS History
8 records (8 active, 0 former)
●NSns1.digitalocean.com2026-08-19 → 2026-09-03 · 2 obs
● 2026-09-03 20:54:04
●NSns2.digitalocean.com2026-08-19 → 2026-09-03 · 2 obs
● 2026-09-03 20:54:04
●NSns3.digitalocean.com2026-08-19 → 2026-09-03 · 2 obs
● 2026-09-03 20:54:04
●MXalt1.aspmx.l.google.com2026-08-19 → 2026-09-03 · 2 obs
● 2026-09-03 20:54:04
●MXalt2.aspmx.l.google.com2026-08-19 → 2026-09-03 · 2 obs
● 2026-09-03 20:54:04
●MXalt3.aspmx.l.google.com2026-08-19 → 2026-09-03 · 2 obs
● 2026-09-03 20:54:04
●MXalt4.aspmx.l.google.com2026-08-19 → 2026-09-03 · 2 obs
● 2026-09-03 20:54:04
●MXaspmx.l.google.com2026-08-19 → 2026-09-03 · 2 obs
● 2026-09-03 20:54:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| securitycogs.com | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | 3 records |
✅ Authoritative Response
Server:172.64.52.210
NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for securitycogs.com (unsigned zone)
⏱️ Timing
Total: 353ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 3 | ns1.digitalocean.com, ns2.digitalocean.com... |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns1.digitalocean.com hostmaster.security |
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)
Analysis
Name Servers
securitycogs.com carries NS records delegating to ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.
securitycogs.com has at least partial name server overlap with other domains, such as mmogamers.net, xn--rtelmezsztr-t7a7g3gp2d.hu, mobiclient.com and two others.
It is common to find these name servers paired with the name servers ns4.digitalocean.com.
ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com are three hostnames that each resolve to a pair of IP addresses: ns1.digitalocean.com to 172.64.52.210 and 2606:4700:52::ac40:34d2, ns2.digitalocean.com to 172.64.53.21 and 2606:4700:5a::ac40:3515, and ns3.digitalocean.com to 172.64.49.209 and 2606:4700:52::ac40:31d1.
Mail Servers
Mail for securitycogs.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by securitycogs.com are shared with other domains: eleganthardware.in, tatisoko.com, livinghopecenters.org and two others among them.
These mail servers often appear in conjunction with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names pointing to two IP addresses:
aspmx.l.google.com resolves to two addresses: 192.178.155.26 and 2607:f8b0:4004:c1b::1a.
alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.27 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1a.