`machikagi.com`

DNSSEC	⚠️ Not signed
A	54.238.137.11^{🇯🇵 Amazon54.238.128.0/17 EC2 NRT prefix}
		PTR	`ec2-54-238-137-11.ap-northeast-1.compute.amazonaws.com`
NS	`ns-397.awsdns-49.com` ⭐
		A	2600:9000:5301:8d00::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-397.awsdns-49.com`
		A	205.251.193.141^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-397.awsdns-49.com`
NS	`ns-1041.awsdns-02.org`
		A	2600:9000:5304:1100::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1041.awsdns-02.org`
		A	205.251.196.17^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1041.awsdns-02.org`
NS	`ns-1726.awsdns-23.co.uk`
		A	2600:9000:5306:be00::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1726.awsdns-23.co.uk`
		A	205.251.198.190^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1726.awsdns-23.co.uk`
NS	`ns-883.awsdns-46.net`
		A	2600:9000:5303:7300::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-883.awsdns-46.net`
		A	205.251.195.115^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-883.awsdns-46.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	172.253.62.27^{🇺🇸 Google172.253.62.0/24}
			PTR	`bc-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`/t0DCm6ejENnuyQ3E9ItSM+N2Ia57C93HxtcEvGqWc4=`
SOA	`ns-397.awsdns-49.com`awsdns-hostmaster@amazon.com serial=1

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

Same first word

machikagi.com

DNS History

10 records (10 active, 0 former)

●NSns-1041.awsdns-02.org2016-12-16 → 2026-08-14 · 2 obs

● 2016-12-16 14:34:32
● 2026-08-14 20:19:10

●NSns-1726.awsdns-23.co.uk2016-12-16 → 2026-08-14 · 2 obs

● 2016-12-16 14:34:32
● 2026-08-14 20:19:10

●NSns-397.awsdns-49.com2016-12-16 → 2026-08-14 · 2 obs

● 2016-12-16 14:34:32
● 2026-08-14 20:19:10

●NSns-883.awsdns-46.net2016-12-16 → 2026-08-14 · 2 obs

● 2016-12-16 14:34:32
● 2026-08-14 20:19:10

●MXalt1.aspmx.l.google.com2016-12-16 → 2026-08-14 · 2 obs

● 2016-12-16 14:34:32
● 2026-08-14 20:19:10

●MXalt2.aspmx.l.google.com2016-12-16 → 2026-08-14 · 2 obs

● 2016-12-16 14:34:32
● 2026-08-14 20:19:10

●MXaspmx.l.google.com2016-12-16 → 2026-08-14 · 2 obs

● 2016-12-16 14:34:32
● 2026-08-14 20:19:10

●MXaspmx2.googlemail.com2016-12-16 → 2026-08-14 · 2 obs

● 2016-12-16 14:34:32
● 2026-08-14 20:19:10

●MXaspmx3.googlemail.com2016-12-16 → 2026-08-14 · 2 obs

● 2016-12-16 14:34:32
● 2026-08-14 20:19:10

●A54.238.137.112016-12-16 → 2026-08-14 · 2 obs

● 2016-12-16 14:34:32
● 2026-08-14 20:19:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
machikagi.com	ns-397.awsdns-49.com, ns-883.awsdns-46.net, ns-1041.awsdns-02.org, ns-1726.awsdns-23.co.uk	2 records

✅ Authoritative Response

Server:205.251.193.141

NS records: ns-397.awsdns-49.com, ns-883.awsdns-46.net, ns-1041.awsdns-02.org, ns-1726.awsdns-23.co.uk

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for machikagi.com (unsigned zone)

⏱️ Timing

Total: 392ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.238.137.11`
NS	4	`ns-1041.awsdns-02.org, ns-1726.awsdns-23.co.uk...`
MX	5	`aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)...`
TXT	1	`/t0DCm6ejENnuyQ3E9ItSM+N2Ia57C93HxtcEvGq`
SOA	1	`ns-397.awsdns-49.com awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-397.awsdns-49.com, ns-397.awsdns-49.com)

Analysis

IP Addresses

machikagi.com resolves to just one IP address, 54.238.137.11.

ec2-54-238-137-11.ap-northeast-1.compute.amazonaws.com is an example of another host name that shares IP numbers with machikagi.com.

Name Servers

The NS records for machikagi.com point to four name servers: ns-397.awsdns-49.com, ns-883.awsdns-46.net, ns-1041.awsdns-02.org and ns-1726.awsdns-23.co.uk.

machikagi.com has at least partial name server overlap with other domains, such as isp99.com, haemophiliagateway.org, ibadda.com and two others.

These name servers tend to appear together with the name servers ns-396.awsdns-49.com, ns-701.awsdns-23.net and ns-1583.awsdns-05.co.uk.

ns-397.awsdns-49.com, ns-883.awsdns-46.net, ns-1041.awsdns-02.org and ns-1726.awsdns-23.co.uk all point to exactly two IP numbers each: ns-397.awsdns-49.com → 205.251.193.141 and 2600:9000:5301:8d00::1; ns-883.awsdns-46.net → 205.251.195.115 and 2600:9000:5303:7300::1; ns-1041.awsdns-02.org → 205.251.196.17 and 2600:9000:5304:1100::1; ns-1726.awsdns-23.co.uk → 205.251.198.190 and 2600:9000:5306:be00::1.