`cre-token.com`

DNSSEC	⚠️ Not signed
NS	`asns1.customer.ne.jp` ⭐
		A	210.150.254.86^{🇯🇵 InfoSphere210.150.0.0/16 INFOSPHERE}
			PTR	`asns1.customer.ne.jp`
NS	`asns2.customer.ne.jp`
		A	210.150.254.94^{🇯🇵 InfoSphere210.150.0.0/16 INFOSPHERE}
			PTR	`asns2.customer.ne.jp`
MX	`cretoken-com0i.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:cc1a::^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-tycp286cu02600.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1a::3^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-tyvp286cu00203.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1f::1^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-os0p286cu01201.inbound.protection.outlook.com`
		A	2a01:111:f403:cc24::^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-os0p286cu01300.inbound.protection.outlook.com`
		A	52.101.124.0^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-tycp286cu02600.inbound.protection.outlook.com`
		A	52.101.124.5^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-tyvp286cu00305.inbound.protection.outlook.com`
		A	52.101.157.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-os0p286cu01302.inbound.protection.outlook.com`
		A	52.101.157.11^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-os0p286cu01203.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.mta.hdems.com include:spf.protection.outlook.com ip4:153.1...`
SOA	`asns1.customer.ne.jp`tms_idc_maintenance@m.agrex.co.jp serial=1528687918

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

cre-token.com

centre-ok.com

ok-center.ru

ok-center.cn

e-koncert.dk

3 records (3 active, 0 former)

●NSasns1.customer.ne.jp2018-06-12 → 2026-05-12 · 2 obs

● 2018-06-12 14:54:06
● 2026-05-12 10:47:16

●NSasns2.customer.ne.jp2018-06-12 → 2026-05-12 · 2 obs

● 2018-06-12 14:54:06
● 2026-05-12 10:47:16

●MXcretoken-com0i.mail.protection.outlook.com2026-04-06 → 2026-05-12 · 2 obs

● 2026-04-06 15:04:16
● 2026-05-12 10:47:16

cre-token.com is delegated to two name servers: asns1.customer.ne.jp and asns2.customer.ne.jp.

cre-token.com shares the same name server setup as other domains, for example v3900-234.mailsecure.jp, v0802-023.mailsecure.jp, seiko-co.co.jp, jamail.hyogo.jp and gaws.jp.

cre-token.com partially shares name servers with other domains, for instance ns1.properst.co.jp, biwako-marriott.com, nissin-ref.co.jp and aplawjapan.com.

Host names with one IP number:

cre-token.com is handled by a single mail server, cretoken-com0i.mail.protection.outlook.com.