securityforcemonitor.org - robtex.com
securityforcemonitor.org
org
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.org.afilias-nst.info ⭐ ⚠️ Not in parent delegation | ||||||
| NS | a2.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | b0.org.afilias-nst.org | ||||||
| NS | b2.org.afilias-nst.org | ||||||
| NS | c0.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | d0.org.afilias-nst.org | ||||||
| SOA | a0.org.afilias-nst.infohostmaster@donuts.email serial=1776097906 | ||||||
Same first word
securityforcemonitor.org |
DNS History
10 records (10 active, 0 former)
●NSns1.wordpress.com2026-03-20 → 2026-04-13 · 2 obs
● 2026-04-13 16:58:42
●NSns2.wordpress.com2026-03-20 → 2026-04-13 · 2 obs
● 2026-04-13 16:58:42
●NSns3.wordpress.com2026-03-20 → 2026-04-13 · 2 obs
● 2026-04-13 16:58:42
●MXalt1.aspmx.l.google.com2026-03-20 → 2026-04-13 · 2 obs
● 2026-04-13 16:58:42
●MXalt2.aspmx.l.google.com2026-03-20 → 2026-04-13 · 2 obs
● 2026-04-13 16:58:42
●MXaspmx.l.google.com2026-03-20 → 2026-04-13 · 2 obs
● 2026-04-13 16:58:42
●MXaspmx2.googlemail.com2026-03-20 → 2026-04-13 · 2 obs
● 2026-04-13 16:58:42
●MXaspmx3.googlemail.com2026-03-20 → 2026-04-13 · 2 obs
● 2026-04-13 16:58:42
●A192.0.78.1342026-03-20 → 2026-04-13 · 2 obs
● 2026-04-13 16:58:42
●A192.0.78.2132026-03-20 → 2026-04-13 · 2 obs
● 2026-04-13 16:58:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| org | b0.org.afilias-nst.org, d0.org.afilias-nst.org, b2.org.afilias-nst.org | - |
| securityforcemonitor.org | ns3.wordpress.com, ns1.wordpress.com, ns2.wordpress.com | - |
✅ Authoritative Response
Server:192.0.74.9
NS records: ns3.wordpress.com, ns1.wordpress.com, ns2.wordpress.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for securityforcemonitor.org (unsigned zone)
⏱️ Timing
Total: 478ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 192.0.78.213, 192.0.78.134 |
| NS | 3 | ns3.wordpress.com, ns2.wordpress.com... |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), aspmx2.googlemail.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.wpcloud.com ~all |
| SOA | 1 | ns1.wordpress.com hostmaster.wordpress.c |
Analysis
IP Addresses
securityforcemonitor.org resolves to two IP numbers: 192.0.78.134 and 192.0.78.213.
Other host names, for instance argument.sk, acdc-power.fr, huangchi.com.tw, pitchmark.com and risktrak.com share IP numbers with securityforcemonitor.org.
Name Servers
securityforcemonitor.org is delegated to three name servers: ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com.
securityforcemonitor.org partially shares name servers with other domains; examples include monumentroofer.com, meridianrehab.ca, ringtalesontheroad.com, artsofcorporation.org and gardencare-services.co.uk.
Host names with two IP numbers:
ns1.wordpress.com points to 2a04:fa87:ffff::c6b5:7409 and 198.181.116.9.
ns2.wordpress.com points to 2a04:fa87:ffff::c6b5:7509 and 198.181.117.9.
ns3.wordpress.com points to 2620:115:c00f::c000:4a09 and 192.0.74.9.
Mail Servers
Five mail servers handle securityforcemonitor.org: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
securityforcemonitor.org shares some mail servers with other domains, at least partially, such as themasters.co, pelotonmarketing.co.nz, chbsllc.com, glpwd.com and acaplam.com.br.
These mail servers are often used with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx2.googlemail.com points to: 2a00:1450:4025:402::1a and 142.250.102.26
aspmx3.googlemail.com points to: 2a00:1450:400b:c02::1b and 172.253.116.27
aspmx.l.google.com points to: 2607:f8b0:4004:c1d::1b and 172.253.115.26
alt1.aspmx.l.google.com points to: 2607:f8b0:4023:2801::1b and 192.178.128.26
alt2.aspmx.l.google.com points to: 2607:f8b0:4023:1015::1a and 172.253.135.26