securityforce.in - dns.ninja
securityforce.in
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns.trs-dns.com ⭐ | ||||||
| NS | ns1.registry.in | ||||||
| NS | ns2.registry.in ⚠️ Not in parent delegation | ||||||
| NS | ns3.registry.in | ||||||
| NS | ns4.registry.in ⚠️ Not in parent delegation | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1782594360 | ||||||
Same first word
Similar names
forcesecurity.com |
forcesecurity.com.br |
forcesecurity.com.au |
forcesecurity.ca |
sourcecertify.com |
forcesecurity.net |
forcesecurity.cz |
DNS History
11 records (8 active, 3 former)
○NSns1.crazydomains.com2015-05-28 → 2017-06-13 · 3 obs
● 2017-06-13 03:33:34
○ 2026-06-27 21:37:00
○NSns2.crazydomains.com2015-05-28 → 2017-06-13 · 3 obs
● 2017-06-13 03:33:34
○ 2026-06-27 21:37:00
●NSns41.domaincontrol.com2026-06-27 → 2026-06-27 · 2 obs
● 2026-06-27 21:37:00
●NSns42.domaincontrol.com2026-06-27 → 2026-06-27 · 2 obs
● 2026-06-27 21:37:00
●MXalt1.aspmx.l.google.com2026-06-27 → 2026-06-27 · 1 obs
●MXalt2.aspmx.l.google.com2026-06-27 → 2026-06-27 · 1 obs
●MXalt3.aspmx.l.google.com2026-06-27 → 2026-06-27 · 1 obs
●MXalt4.aspmx.l.google.com2026-06-27 → 2026-06-27 · 1 obs
●MXaspmx.l.google.com2026-06-27 → 2026-06-27 · 1 obs
●A13.202.32.1752026-06-27 → 2026-06-27 · 2 obs
● 2026-06-27 21:37:00
○A203.170.80.2502015-05-28 → 2017-06-13 · 3 obs
● 2017-06-13 03:33:34
○ 2026-06-27 21:37:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns1.registry.in, ns3.registry.in | - |
| securityforce.in | ns41.domaincontrol.com, ns42.domaincontrol.com | - |
✅ Authoritative Response
Server:97.74.100.21
NS records: ns41.domaincontrol.com, ns42.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for securityforce.in (unsigned zone)
⏱️ Timing
Total: 230ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 13.202.32.175 |
| NS | 2 | ns41.domaincontrol.com, ns42.domaincontrol.com |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)... |
| TXT | 3 | v=spf1 include:dc-aa8e722993._spfm.secur, facebook-domain-verification=sjw4bw03c3l... |
| SOA | 1 | ns41.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
securityforce.in directs to one IP number, which is 13.202.32.175.
Among the host names that share IP numbers with securityforce.in is ec2-13-202-32-175.ap-south-1.compute.amazonaws.com, as one example.
Name Servers
The NS records for securityforce.in delegate to ns41.domaincontrol.com and ns42.domaincontrol.com.
securityforce.in has the same name server delegation as a number of other domains, such as romulusent.com, ahernpoolsandspas.com, waterloo.dental and two more.
ns41.domaincontrol.com resolves to 97.74.100.21 and 2603:5:2142::15. Likewise, ns42.domaincontrol.com resolves to 173.201.68.21 and 2603:5:2242::15 — two IP addresses apiece.
Mail Servers
securityforce.in is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
securityforce.in shares at least some of its mail servers with other domains — for example luxehome.nl, 2fifty4.nl, zitec.com and two more.
It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.
Hosts with two IP numbers each:
The A records for aspmx.l.google.com return 142.251.167.26 and 2607:f8b0:4004:c23::1a.
The A records for alt1.aspmx.l.google.com return 108.177.123.26 and 2800:3f0:4003:c0f::1b.
The A records for alt2.aspmx.l.google.com return 172.253.116.26 and 2a00:1450:400b:c02::1b.
The A records for alt3.aspmx.l.google.com return 192.178.223.26 and 2a00:1450:4009:c0f::1b.
The A records for alt4.aspmx.l.google.com return 172.253.157.27 and 2a00:1450:400c:c23::1a.