`designforsecurity.org`

DNSSEC	⚠️ Not signed
A	157.245.43.8^{🇬🇧 DIGITALOCEAN157.245.32.0/20 DigitalOcean}
		PTR	`crow.c2office.uk`
NS	`ns31.domaincontrol.com` ⭐
		A	2603:5:2191::10^{🇺🇸 GODADDY-DNS2603:5:2190::/44}
			PTR	`ns31.domaincontrol.com`
		A	97.74.105.16^{🇺🇸 GODADDY-DNS97.74.104.0/23}
			PTR	`ns31.domaincontrol.com`
NS	`ns32.domaincontrol.com`
		A	2603:5:2291::10^{🇺🇸 GODADDY-DNS2603:5:2290::/44}
			PTR	`ns32.domaincontrol.com`
		A	173.201.73.16^{🇺🇸 GODADDY-DNS173.201.72.0/23}
			PTR	`ns32.domaincontrol.com`
MX	`designforsecurity-org.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:ca0b::^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-lo2p265cu02300.inbound.protection.outlook.com`
		A	2a01:111:f403:ca0b::2^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-lo0p265cu00202.inbound.protection.outlook.com`
		A	2a01:111:f403:ca1a::^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-cwxp265cu00500.inbound.protection.outlook.com`
		A	2a01:111:f403:ca1a::1^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-cwxp265cu00601.inbound.protection.outlook.com`
		A	52.101.89.1^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-lo0p265cu00201.inbound.protection.outlook.com`
		A	52.101.89.2^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-lo3p265cu00302.inbound.protection.outlook.com`
		A	52.101.99.0^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cwxp265cu00600.inbound.protection.outlook.com`
		A	52.101.99.2^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cwxp265cu00502.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.mandrillapp.com all`
TXT	`MS=ms96404854`
SOA	`ns31.domaincontrol.com`dns@jomax.net 2025-08-20 #1

`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.info`hostmaster@donuts.email serial=1778692569

PTR for

189.120.82.80.in-addr.arpa

Same first word

designforsecurity.org

DNS History

15 records (4 active, 11 former)

○NSns.mainnameserver.com2016-12-30 → 2018-01-14 · 5 obs

○ 2016-03-10 12:03:58
● 2016-12-30 10:14:24
● 2018-01-14 05:38:00
○ 2026-03-29 21:49:00
○ 2026-05-13 17:42:34

○NSns.srv2.com2015-08-02 → 2016-03-10 · 4 obs

● 2015-08-02 08:24:38
● 2016-03-10 12:03:58
○ 2016-12-30 10:14:24
○ 2026-05-13 17:42:34

○NSns2.mainnameserver.com2016-12-30 → 2018-01-14 · 5 obs

○ 2016-03-10 12:03:58
● 2016-12-30 10:14:24
● 2018-01-14 05:38:00
○ 2026-03-29 21:49:00
○ 2026-05-13 17:42:34

○NSns2.srv2.com2015-08-02 → 2016-03-10 · 4 obs

● 2015-08-02 08:24:38
● 2016-03-10 12:03:58
○ 2016-12-30 10:14:24
○ 2026-05-13 17:42:34

●NSns31.domaincontrol.com2026-03-29 → 2026-05-13 · 3 obs

○ 2018-01-14 05:38:00
● 2026-03-29 21:49:00
● 2026-05-13 17:42:34

●NSns32.domaincontrol.com2026-03-29 → 2026-05-13 · 3 obs

○ 2018-01-14 05:38:00
● 2026-03-29 21:49:00
● 2026-05-13 17:42:34

●MXdesignforsecurity-org.mail.protection.outlook.com2026-03-29 → 2026-05-13 · 3 obs

○ 2018-01-14 05:38:00
● 2026-03-29 21:49:00
● 2026-05-13 17:42:34

○MXmail.designforsecurity.org2016-12-30 → 2018-01-14 · 5 obs

○ 2016-03-10 12:03:58
● 2016-12-30 10:14:24
● 2018-01-14 05:38:00
○ 2026-03-29 21:49:00
○ 2026-05-13 17:42:34

○MXmail.gmp.police.uk2015-08-02 → 2016-03-10 · 4 obs

● 2015-08-02 08:24:38
● 2016-03-10 12:03:58
○ 2016-12-30 10:14:24
○ 2026-05-13 17:42:34

○MXmail1.gmp.police.uk2015-08-02 → 2016-03-10 · 4 obs

● 2015-08-02 08:24:38
● 2016-03-10 12:03:58
○ 2016-12-30 10:14:24
○ 2026-05-13 17:42:34

○MXmail2.gmp.police.uk2015-08-02 → 2016-03-10 · 4 obs

● 2015-08-02 08:24:38
● 2016-03-10 12:03:58
○ 2016-12-30 10:14:24
○ 2026-05-13 17:42:34

○MXmail3.gmp.police.uk2015-08-02 → 2016-03-10 · 4 obs

● 2015-08-02 08:24:38
● 2016-03-10 12:03:58
○ 2016-12-30 10:14:24
○ 2026-05-13 17:42:34

●A157.245.43.82026-03-29 → 2026-05-13 · 3 obs

○ 2018-01-14 05:38:00
● 2026-03-29 21:49:00
● 2026-05-13 17:42:34

○A176.32.230.512016-12-30 → 2018-01-14 · 5 obs

○ 2016-03-10 12:03:58
● 2016-12-30 10:14:24
● 2018-01-14 05:38:00
○ 2026-03-29 21:49:00
○ 2026-05-13 17:42:34

○A5.159.224.92015-08-02 → 2016-03-10 · 4 obs

● 2015-08-02 08:24:38
● 2016-03-10 12:03:58
○ 2016-12-30 10:14:24
○ 2026-05-13 17:42:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
org	b0.org.afilias-nst.org, b2.org.afilias-nst.org, d0.org.afilias-nst.org	-
designforsecurity.org	ns31.domaincontrol.com, ns32.domaincontrol.com	-

✅ Authoritative Response

Server:97.74.105.16

NS records: ns31.domaincontrol.com, ns32.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for designforsecurity.org (unsigned zone)

⏱️ Timing

Total: 1599ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`157.245.43.8`
NS	2	`ns31.domaincontrol.com, ns32.domaincontrol.com`
MX	1	`designforsecurity-org.mail.protection.ou`
TXT	2	`v=spf1 include:spf.mandrillapp.com all, MS=ms96404854`
SOA	1	`ns31.domaincontrol.com dns.jomax.net`

Analysis

IP Addresses

designforsecurity.org points to a single IP address: 157.245.43.8.

Other host names, for instance crow.c2office.uk, share IP numbers with designforsecurity.org.

Name Servers

designforsecurity.org is delegated to two name servers: ns31.domaincontrol.com and ns32.domaincontrol.com.

designforsecurity.org uses the same name server setup as other domains, including track-os.com, jimselectric.com, sultrysultan.com, classjewelers.com and ista.co.uk.

Host names with two IP numbers:

ns31.domaincontrol.com points to 2603:5:2191::10 and 97.74.105.16.

ns32.domaincontrol.com points to 2603:5:2291::10 and 173.201.73.16.

Mail Servers

The mail server for designforsecurity.org is designforsecurity-org.mail.protection.outlook.com.

designforsecurity-org.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:ca0b::, 2a01:111:f403:ca0b::2, 2a01:111:f403:ca1a::, 2a01:111:f403:ca1a::1, 52.101.89.1, 52.101.89.2, 52.101.99.0 and 52.101.99.2.

designforsecurity.org - robtex.com