`flameandwatch.com`

DNSSEC	⚠️ Not signed
A	2400:8902::f03c:93ff:fed2:9dfb^{🇯🇵 AKAMAI-LINODE-AP2400:8902::/32 Akamai Technologies}
		PTR	`nanami.blaze.ph`
A	170.187.223.168^{🇯🇵 AKAMAI-LINODE-AP170.187.208.0/20 Akamai Technologies}
NS	`ns1.blaze.ph` ⭐
		A	2400:8902::f03c:93ff:fed2:9dfb^{🇯🇵 AKAMAI-LINODE-AP2400:8902::/32 Akamai Technologies}
			PTR	`nanami.blaze.ph`
		A	170.187.223.168^{🇯🇵 AKAMAI-LINODE-AP170.187.208.0/20 Akamai Technologies}
			PTR	`nanami.blaze.ph`
NS	`ns2.blaze.ph`
		A	2a01:7e00::f03c:93ff:fed2:9d03^{🇬🇧 AKAMAI-LINODE-AP2a01:7e00::/32 Akamai Technologies}
			PTR	`yukino.blaze.ph`
		A	143.42.253.201^{🇬🇧 AKAMAI-LINODE-AP143.42.240.0/20 Akamai Technologies}
			PTR	`yukino.blaze.ph`
MX	`nanami.blaze.ph` ⭐
		A	2400:8902::f03c:93ff:fed2:9dfb^{🇯🇵 AKAMAI-LINODE-AP2400:8902::/32 Akamai Technologies}
			PTR	`nanami.blaze.ph`
		A	170.187.223.168^{🇯🇵 AKAMAI-LINODE-AP170.187.208.0/20 Akamai Technologies}
			PTR	`nanami.blaze.ph`
MX	`yukino.blaze.ph`⁽¹⁰⁾
		A	2a01:7e00::f03c:93ff:fed2:9d03^{🇬🇧 AKAMAI-LINODE-AP2a01:7e00::/32 Akamai Technologies}
			PTR	`yukino.blaze.ph`
		A	143.42.253.201^{🇬🇧 AKAMAI-LINODE-AP143.42.240.0/20 Akamai Technologies}
			PTR	`yukino.blaze.ph`
TXT	`v=spf1 mx -all`
TXT	`google-site-verification=hJt2obrPTpHcHsiyXzOmwy918BC-fG0H-evizCFwthE`
SOA	`ns1.blaze.ph`hostmaster@flameandwatch.com 2025-08-30 #0

`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=1771291435

Same first word

flameandwatch.com

DNS History

16 records (6 active, 10 former)

●NSns1.blaze.ph2026-03-08 → 2026-03-23 · 3 obs

○ 2017-10-12 14:27:18
● 2026-03-08 19:12:26
● 2026-03-23 02:29:40

○NSns1.linode.com2016-12-14 → 2017-10-12 · 4 obs

● 2016-12-14 22:54:16
● 2017-10-12 14:27:18
○ 2026-03-08 19:12:26
○ 2026-03-23 02:29:40

●NSns2.blaze.ph2026-03-08 → 2026-03-23 · 3 obs

○ 2017-10-12 14:27:18
● 2026-03-08 19:12:26
● 2026-03-23 02:29:40

○NSns2.linode.com2016-12-14 → 2017-10-12 · 4 obs

● 2016-12-14 22:54:16
● 2017-10-12 14:27:18
○ 2026-03-08 19:12:26
○ 2026-03-23 02:29:40

○NSns3.linode.com2016-12-14 → 2017-10-12 · 4 obs

● 2016-12-14 22:54:16
● 2017-10-12 14:27:18
○ 2026-03-08 19:12:26
○ 2026-03-23 02:29:40

○NSns4.linode.com2016-12-14 → 2017-10-12 · 4 obs

● 2016-12-14 22:54:16
● 2017-10-12 14:27:18
○ 2026-03-08 19:12:26
○ 2026-03-23 02:29:40

○NSns5.linode.com2016-12-14 → 2017-10-12 · 4 obs

● 2016-12-14 22:54:16
● 2017-10-12 14:27:18
○ 2026-03-08 19:12:26
○ 2026-03-23 02:29:40

●MXnanami.blaze.ph2026-03-08 → 2026-03-23 · 3 obs

○ 2017-10-12 14:27:18
● 2026-03-08 19:12:26
● 2026-03-23 02:29:40

○MXnanami.blazeph.lol2016-12-14 → 2017-10-12 · 4 obs

● 2016-12-14 22:54:16
● 2017-10-12 14:27:18
○ 2026-03-08 19:12:26
○ 2026-03-23 02:29:40

●MXyukino.blaze.ph2026-03-08 → 2026-03-23 · 3 obs

○ 2017-10-12 14:27:18
● 2026-03-08 19:12:26
● 2026-03-23 02:29:40

○A139.162.75.872016-12-14 → 2017-10-12 · 4 obs

● 2016-12-14 22:54:16
● 2017-10-12 14:27:18
○ 2026-03-08 19:12:26
○ 2026-03-23 02:29:40

○A143.42.253.2012026-03-08 → 2026-03-08 · 4 obs

○ 2017-10-12 14:27:18
● 2026-03-08 19:12:26
○ 2026-03-20 08:41:44
○ 2026-03-23 02:29:40

●A170.187.223.1682026-03-20 → 2026-03-23 · 3 obs

○ 2026-03-08 19:12:26
● 2026-03-20 08:41:44
● 2026-03-23 02:29:40

○A2400:8902::f03c:91ff:fee0:466b2016-12-14 → 2017-10-12 · 4 obs

● 2016-12-14 22:54:16
● 2017-10-12 14:27:18
○ 2026-03-08 19:12:26
○ 2026-03-23 02:29:40

●A2400:8902::f03c:93ff:fed2:9dfb2026-03-23 → 2026-03-23 · 3 obs

○ 2026-03-08 19:12:26
○ 2026-03-20 08:41:44
● 2026-03-23 02:29:40

○A2a01:7e00::f03c:93ff:fed2:9d032026-03-08 → 2026-03-20 · 4 obs

○ 2017-10-12 14:27:18
● 2026-03-08 19:12:26
● 2026-03-20 08:41:44
○ 2026-03-23 02:29:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, j.gtld-servers.net, i.gtld-servers.net, h.gtld-servers.net...	-
flameandwatch.com	ns1.blaze.ph, ns2.blaze.ph	-

✅ Authoritative Response

Server:143.42.253.201

NS records: ns1.blaze.ph, ns2.blaze.ph

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for flameandwatch.com (unsigned zone)

⏱️ Timing

Total: 1137ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`170.187.223.168`
AAAA	1	`2a01:7e00::f03c:93ff:fed2:9d03`
NS	2	`ns2.blaze.ph, ns1.blaze.ph`
MX	2	`yukino.blaze.ph (pri: 10), nanami.blaze.ph (pri: 5)`
TXT	2	`google-site-verification=hJt2obrPTpHcHsi, v=spf1 mx -all`
SOA	1	`ns1.blaze.ph hostmaster.flameandwatch.co`

Analysis

IP Addresses

flameandwatch.com resolves to two IP numbers: 2400:8902::f03c:93ff:fed2:9dfb and 170.187.223.168.

Other host names, for instance, ns1.blaze.ph, nanami.blaze.ph, blaze.ph and blazeph.lol share IP numbers with flameandwatch.com.

Name Servers

flameandwatch.com has two name servers: ns1.blaze.ph and ns2.blaze.ph.

flameandwatch.com uses the same name server setup as other domains, for example blazeph.lol and blaze.ph.

Host names with two IP numbers:

ns1.blaze.ph points to: 2400:8902::f03c:93ff:fed2:9dfb and 170.187.223.168; ns2.blaze.ph points to: 2a01:7e00::f03c:93ff:fed2:9d03 and 143.42.253.201.

Mail Servers

flameandwatch.com is served by two mail servers: nanami.blaze.ph and yukino.blaze.ph.

flameandwatch.com shares the same mail server setup as other domains, for instance blaze.ph and blazeph.lol.

Host names with two IP numbers:

nanami.blaze.ph points to: 2400:8902::f03c:93ff:fed2:9dfb and 170.187.223.168; yukino.blaze.ph points to: 2a01:7e00::f03c:93ff:fed2:9d03 and 143.42.253.201.

flameandwatch.com - robtex.com