`dd0ss-waf.com`

DNSSEC	⚠️ Not signed
NS	`ns1.ddoss-waf.com` ⭐ ⚠️ Not in parent delegation
		A	47.109.31.80^{🇨🇳 Alibaba-Cloud47.109.0.0/16}
NS	`ns1.dd0ss-waf.com` ⚠️ Not in zone NS records
		A	47.109.31.80^{🇨🇳 Alibaba-Cloud47.109.0.0/16}
		A	121.37.230.116^{🇨🇳 HWCSNET121.37.192.0/18 Huawei Clouds Guangzhou Region}
			PTR	`ecs-121-37-230-116.compute.hwclouds-dns.com`
NS	`ns2.dd0ss-waf.com` ⚠️ Not in zone NS records
		A	47.109.31.80^{🇨🇳 Alibaba-Cloud47.109.0.0/16}
		A	121.37.230.116^{🇨🇳 HWCSNET121.37.192.0/18 Huawei Clouds Guangzhou Region}
			PTR	`ecs-121-37-230-116.compute.hwclouds-dns.com`
NS	`ns2.ddoss-waf.com` ⚠️ Not in parent delegation
		A	121.37.230.116^{🇨🇳 HWCSNET121.37.192.0/18 Huawei Clouds Guangzhou Region}
			PTR	`ecs-121-37-230-116.compute.hwclouds-dns.com`
SOA	`ns1.ddoss-waf.com`zeus@bb2.com serial=1773223023

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

Subdomains

ns1.dd0ss-waf.com

ns2.dd0ss-waf.com

Same first word

dd0ss-waf.com

DNS History

4 records (4 active, 0 former)

●NSns1.dd0ss-waf.com2026-06-11 → 2026-07-14 · 2 obs

● 2026-06-11 11:31:14
● 2026-07-14 09:43:38

●NSns1.ddoss-waf.com2026-06-11 → 2026-07-14 · 4 obs

● 2026-06-11 11:31:14
○ 2026-07-08 07:00:40
● 2026-07-14 09:43:36
● 2026-07-14 09:43:38

●NSns2.dd0ss-waf.com2026-06-11 → 2026-07-14 · 2 obs

● 2026-06-11 11:31:14
● 2026-07-14 09:43:38

●NSns2.ddoss-waf.com2026-06-11 → 2026-07-14 · 4 obs

● 2026-06-11 11:31:14
○ 2026-07-08 07:00:40
● 2026-07-14 09:43:36
● 2026-07-14 09:43:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
dd0ss-waf.com	ns1.dd0ss-waf.com, ns2.dd0ss-waf.com	4 records

✅ Authoritative Response

Server:121.37.230.116

NS records: ns1.dd0ss-waf.com, ns2.dd0ss-waf.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dd0ss-waf.com (unsigned zone)

⏱️ Timing

Total: 3573ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.ddoss-waf.com, ns2.ddoss-waf.com`
SOA	1	`ns1.ddoss-waf.com zeus.bb2.com`

📌 Glue Records Collected

Total: 4

In-bailiwick: 4 (ns1.dd0ss-waf.com, ns1.dd0ss-waf.com, ns2.dd0ss-waf.com...)

Analysis

Hierarchy

ns1.dd0ss-waf.com and ns2.dd0ss-waf.com are both subdomains of dd0ss-waf.com.

Name Servers

The authoritative name servers for dd0ss-waf.com are ns1.dd0ss-waf.com, ns2.dd0ss-waf.com, ns1.ddoss-waf.com and ns2.ddoss-waf.com.

There is at least partial name server overlap between dd0ss-waf.com and other domains — lnxywl.com, alidnsv6.com, xinshux.cn and two more among them.

These name servers regularly appear alongside ns1.cfdns5.com, ns2.cfdns5.com, ns1.tcdns31.com and 7 other name servers in NS record sets.

Hostnames that resolve to two IP addresses:

ns1.dd0ss-waf.com directs traffic to 47.109.31.80 and 121.37.230.116.

ns2.dd0ss-waf.com directs traffic to 47.109.31.80 and 121.37.230.116.

Hosts with just one IP address:

ns1.ddoss-waf.com has the IP address 47.109.31.80.

ns2.ddoss-waf.com has the IP address 121.37.230.116.

The host names ns1.dd0ss-waf.com, ns2.dd0ss-waf.com and ns1.ddoss-waf.com each resolve to 47.109.31.80.

The host names ns1.dd0ss-waf.com, ns2.dd0ss-waf.com and ns2.ddoss-waf.com each resolve to 121.37.230.116.

dd0ss-waf.com - robtex.com

dd0ss-waf.com

com