`sweetshould.net`

DNSSEC	⚠️ Not signed
A	52.16.171.153^{🇮🇪 Amazon52.16.0.0/15 EC2 DUB prefix}
		PTR	`ec2-52-16-171-153.eu-west-1.compute.amazonaws.com`
NS	`ns1.sweetshould.net` ⭐
		A	18.205.186.231^{🇺🇸 Amazon18.204.0.0/14 EC2 IAD prefix}
			PTR	`ec2-18-205-186-231.compute-1.amazonaws.com`
NS	`ns1.csof.net`
		A	18.205.186.231^{🇺🇸 Amazon18.204.0.0/14 EC2 IAD prefix}
			PTR	`ec2-18-205-186-231.compute-1.amazonaws.com`
NS	`ns2.csof.net`
		A	23.21.178.27^{🇺🇸 Amazon23.20.0.0/15 EC2 IAD prefix}
			PTR	`ec2-23-21-178-27.compute-1.amazonaws.com`
NS	`ns3.csof.net`
		A	3.214.185.54^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-214-185-54.compute-1.amazonaws.com`
NS	`ns4.csof.net`
		A	52.20.19.77^{🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix}
			PTR	`ec2-52-20-19-77.compute-1.amazonaws.com`
MX	`mx1.sweetshould.net` ⭐
		A	46.4.12.146^{🇩🇪 Hetzner46.4.0.0/16 HETZNER-RZ-FKS-BLK3}
			PTR	`static.146.12.4.46.clients.your-server.de`
MX	`mx2.sweetshould.net` ⭐
		A	46.4.10.173^{🇩🇪 Hetzner46.4.0.0/16 HETZNER-RZ-FKS-BLK3}
			PTR	`static.173.10.4.46.clients.your-server.de`
TXT	`v=spf1 include:_incspfcheck.mailspike.net ?all`
SOA	`ns1.sweetshould.net`hostmaster@sweetshould.net serial=1778764585

`net`

	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.net`nstld@verisign-grs.com serial=1778764526

⚠️ On DNS blocklist: tif

Subdomains

www.sweetshould.net

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	b.gtld-servers.net, f.gtld-servers.net, a.gtld-servers.net, j.gtld-servers.net...	-
sweetshould.net	ns1.csof.net, ns2.csof.net, ns4.csof.net, ns3.csof.net	4 records

✅ Authoritative Response

Server:52.20.19.77

NS records: ns1.csof.net, ns2.csof.net, ns4.csof.net, ns3.csof.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sweetshould.net (unsigned zone)

⏱️ Timing

Total: 284ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`52.16.171.153`
NS	4	`ns3.csof.net, ns4.csof.net...`
MX	2	`mx2.sweetshould.net (pri: 10), mx1.sweetshould.net (pri: 10)`
TXT	1	`v=spf1 include:_incspfcheck.mailspike.ne`
SOA	1	`ns1.sweetshould.net hostmaster.sweetshou`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.csof.net, ns2.csof.net, ns4.csof.net...)

Analysis

Hierarchy

sweetshould.net is the parent of www.sweetshould.net.

IP Addresses

sweetshould.net points to IP number 52.16.171.153.

For instance, other host names brafz4bcd02b4e39.net, www.b25314579d921273c44846262a7d5409.net, ritulp.com, 26733f54043aa6e4407bb8ced4f2e9d5.com and 227367fe3c709be7fba27c967141ea3a.com share IP numbers with sweetshould.net.

Name Servers

sweetshould.net is delegated to five name servers: ns1.csof.net, ns2.csof.net, ns3.csof.net, ns4.csof.net and ns1.sweetshould.net.

sweetshould.net shares name servers with other domains at least partially, for example 2f9dab1b1661d7ba5c6fbde0350d7a0b.xyz, chinataiw39e9i9ds.com, e950d14d034bfad46d43cee64ad5a893.com, 149-209.rubytel.ru and drivsinfosproduits.info.

These name servers are commonly used together with ns5.csof.net, ns6.csof.net, ns7.csof.net and ns8.csof.net.

Host names with a single IP:

ns1.csof.net points to 18.205.186.231

ns2.csof.net points to 23.21.178.27

ns3.csof.net points to 3.214.185.54

ns4.csof.net points to 52.20.19.77

ns1.sweetshould.net points to 18.205.186.231

Host names pointing to 18.205.186.231: ns1.csof.net, ns1.sweetshould.net

Mail Servers

Two mail servers mx1.sweetshould.net and mx2.sweetshould.net handle sweetshould.net.

The mail server setup of sweetshould.net is the same as that of other domains, for instance www.sweetshould.net.

Host names with one IP number:

mx1.sweetshould.net points to: 46.4.12.146.

mx2.sweetshould.net points to: 46.4.10.173.

sweetshould.net - robtex.com

sweetshould.net

net