🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`postcode-jp.com`

DNSSEC	⚠️ Not signed
A	151.101.1.195^{🇺🇸 Fastly151.101.0.0/22}
A	151.101.65.195^{🇺🇸 Fastly151.101.64.0/22}
NS	`ns-cloud-d1.googledomains.com` ⭐
		A	2001:4860:4802:32::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d1.googledomains.com`
		A	216.239.32.109^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-d1.googledomains.com`
NS	`ns-cloud-d2.googledomains.com`
		A	2001:4860:4802:34::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d2.googledomains.com`
		A	216.239.34.109^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-d2.googledomains.com`
NS	`ns-cloud-d3.googledomains.com`
		A	2001:4860:4802:36::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d3.googledomains.com`
		A	216.239.36.109^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-d3.googledomains.com`
NS	`ns-cloud-d4.googledomains.com`
		A	2001:4860:4802:38::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d4.googledomains.com`
		A	216.239.38.109^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-d4.googledomains.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	142.251.167.27^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.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.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com include:stspg-customer.com include:send.stripe...`
TXT	`status-page-domain-verification=ktl4mjw9bms2`
TXT	`stripe-verification=d489a7b47449bdac0be614eba870512f56a6429a9efc558b5be46eceb...`
TXT	`google-site-verification=sswrD1TQ44LemSw5bPRn7L5Gdhk7ruW0hemQH2PR-mM`
SOA	`ns-cloud-d1.googledomains.com`cloud-dns-hostmaster@google.com serial=16

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

Same first word

postcode-jp.com

Previous names

Next names

DNS History

23 records (11 active, 12 former)

○NSns-cloud-c1.googledomains.com2018-08-05 → 2018-08-05 · 3 obs

● 2018-08-05 18:29:04
○ 2026-08-29 12:05:22
○ 2026-10-01 16:41:54

○NSns-cloud-c2.googledomains.com2018-08-05 → 2018-08-05 · 3 obs

● 2018-08-05 18:29:04
○ 2026-08-29 12:05:22
○ 2026-10-01 16:41:54

○NSns-cloud-c3.googledomains.com2018-08-05 → 2018-08-05 · 3 obs

● 2018-08-05 18:29:04
○ 2026-08-29 12:05:22
○ 2026-10-01 16:41:54

○NSns-cloud-c4.googledomains.com2018-08-05 → 2018-08-05 · 3 obs

● 2018-08-05 18:29:04
○ 2026-08-29 12:05:22
○ 2026-10-01 16:41:54

●NSns-cloud-d1.googledomains.com2026-08-29 → 2026-10-01 · 3 obs

○ 2018-08-05 18:29:04
● 2026-08-29 12:05:22
● 2026-10-01 16:41:54

●NSns-cloud-d2.googledomains.com2026-08-29 → 2026-10-01 · 3 obs

○ 2018-08-05 18:29:04
● 2026-08-29 12:05:22
● 2026-10-01 16:41:54

●NSns-cloud-d3.googledomains.com2026-08-29 → 2026-10-01 · 3 obs

○ 2018-08-05 18:29:04
● 2026-08-29 12:05:22
● 2026-10-01 16:41:54

●NSns-cloud-d4.googledomains.com2026-08-29 → 2026-10-01 · 3 obs

○ 2018-08-05 18:29:04
● 2026-08-29 12:05:22
● 2026-10-01 16:41:54

●MXalt1.aspmx.l.google.com2026-08-29 → 2026-10-01 · 2 obs

● 2026-08-29 12:05:22
● 2026-10-01 16:41:54

●MXalt2.aspmx.l.google.com2026-08-29 → 2026-10-01 · 2 obs

● 2026-08-29 12:05:22
● 2026-10-01 16:41:54

●MXalt3.aspmx.l.google.com2026-08-29 → 2026-10-01 · 2 obs

● 2026-08-29 12:05:22
● 2026-10-01 16:41:54

●MXalt4.aspmx.l.google.com2026-08-29 → 2026-10-01 · 2 obs

● 2026-08-29 12:05:22
● 2026-10-01 16:41:54

●MXaspmx.l.google.com2026-08-29 → 2026-10-01 · 2 obs

● 2026-08-29 12:05:22
● 2026-10-01 16:41:54

●A151.101.1.1952026-08-29 → 2026-10-01 · 3 obs

○ 2018-08-05 18:29:04
● 2026-08-29 12:05:22
● 2026-10-01 16:41:54

●A151.101.65.1952026-08-29 → 2026-10-01 · 3 obs

○ 2018-08-05 18:29:04
● 2026-08-29 12:05:22
● 2026-10-01 16:41:54

○A2001:4860:4802:32::152018-08-05 → 2018-08-05 · 3 obs

● 2018-08-05 18:29:04
○ 2026-08-29 12:05:22
○ 2026-10-01 16:41:54

○A2001:4860:4802:34::152018-08-05 → 2018-08-05 · 3 obs

● 2018-08-05 18:29:04
○ 2026-08-29 12:05:22
○ 2026-10-01 16:41:54

○A2001:4860:4802:36::152018-08-05 → 2018-08-05 · 3 obs

● 2018-08-05 18:29:04
○ 2026-08-29 12:05:22
○ 2026-10-01 16:41:54

○A2001:4860:4802:38::152018-08-05 → 2018-08-05 · 3 obs

● 2018-08-05 18:29:04
○ 2026-08-29 12:05:22
○ 2026-10-01 16:41:54

○A216.239.32.212018-08-05 → 2018-08-05 · 3 obs

● 2018-08-05 18:29:04
○ 2026-08-29 12:05:22
○ 2026-10-01 16:41:54

○A216.239.34.212018-08-05 → 2018-08-05 · 3 obs

● 2018-08-05 18:29:04
○ 2026-08-29 12:05:22
○ 2026-10-01 16:41:54

○A216.239.36.212018-08-05 → 2018-08-05 · 3 obs

● 2018-08-05 18:29:04
○ 2026-08-29 12:05:22
○ 2026-10-01 16:41:54

○A216.239.38.212018-08-05 → 2018-08-05 · 3 obs

● 2018-08-05 18:29:04
○ 2026-08-29 12:05:22
○ 2026-10-01 16:41:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
postcode-jp.com	ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.32.109

NS records: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for postcode-jp.com (unsigned zone)

⏱️ Timing

Total: 587ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`151.101.1.195, 151.101.65.195`
NS	4	`ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com...`
MX	5	`alt4.aspmx.l.google.com (pri: 10), alt2.aspmx.l.google.com (pri: 5)...`
TXT	4	`v=spf1 include:_spf.google.com include:s, status-page-domain-verification=ktl4mjw9...`
SOA	1	`ns-cloud-d1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-d1.googledomains.com, ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com...)

Analysis

IP Addresses

postcode-jp.com points to the IP addresses 151.101.1.195 and 151.101.65.195

Additional host names — craighorne.co.uk, restopl.us, lfky.app and two others — share IP numbers with postcode-jp.com.

Name Servers

postcode-jp.com has four authoritative name servers: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com.

At least some of postcode-jp.com's name servers are shared with other domains, for example hernextincome.com, hitechelektrik.sk, insurancebolingbrook.com and two more.

Four hostnames, each resolving to a pair of IP addresses: ns-cloud-d1.googledomains.com directs to 216.239.32.109 and 2001:4860:4802:32::6d; ns-cloud-d2.googledomains.com directs to 216.239.34.109 and 2001:4860:4802:34::6d; ns-cloud-d3.googledomains.com directs to 216.239.36.109 and 2001:4860:4802:36::6d; ns-cloud-d4.googledomains.com directs to 216.239.38.109 and 2001:4860:4802:38::6d.

Mail Servers

postcode-jp.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

postcode-jp.com shares mail servers — at least in part — with other domains, including bardsleysfishandchips.co.uk, bossandolly.com, k3-homes.com and two others.

These mail servers are frequently used alongside the mail servers alt4.aspmx.l.google.com, alt3.aspmx.l.google.com and aspmx3.googlemail.com, plus two others.

Host names with two IP numbers:

aspmx.l.google.com directs traffic to 142.251.167.27 and 2607:f8b0:4004:c1b::1a.

alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.