digiper.com - dns.ninja

digiper.com

DNSSEC⚠️ Not signed
A2403:3a00:101:9:219:94:128:165πŸ‡―πŸ‡΅ SAKURA-C2403:3a00::/32 SAKURA Internet // OSAKA BACKBONE 1-8-14 Minami-Honmachi, Chuo-ku, Osaka 541-0054, Japan
PTRwww925.sakura.ne.jp
A219.94.128.165πŸ‡―πŸ‡΅ SAKURA-C219.94.128.0/17 (3/OSAKA) SAKURA Internet // WEST JAPAN BACKBONE 1-8-15 Kyutaro-cho, Chuo Osaka 541-0056, Japan
NSmaster.dns.ne.jp ⭐
A210.224.172.18πŸ‡―πŸ‡΅ SAKURA-C210.224.160.0/19 (1/OSAKA) SAKURA Internet // WEST JAPAN BACKBONE 1-8-15 Kyutaro-cho, Chuo Osaka 541-0056, Japan
PTRmaster.dns.ne.jp
NSns1.dns.ne.jp
A61.211.236.1πŸ‡―πŸ‡΅ SAKURA-B61.211.236.0/24 (4/TOKYO) SAKURA Internet // EAST JAPAN BACKBONE 1-8-15 Kyutaro-cho, Chuo Osaka 541-0056, Japan
PTRns1.dns.ne.jp
NSns2.dns.ne.jp
A133.167.21.1πŸ‡―πŸ‡΅ SAKURA-C133.167.21.0/24 (OSAKA) SAKURA Internet // WEST JAPAN BACKBONE Grand Front Osaka Tower A 35F, 4-20 Ofukacho, Kita-ku, Osaka, Osaka 530-0011, Japan
PTRns2.dns.ne.jp
MXsmtp.google.com ⭐
A2a00:1450:4009:c0f::1aπŸ‡¬πŸ‡§ Google2a00:1450:4009::/48
PTRyulhrs-in-f26.1e100.net
A2a00:1450:4009:c0f::1bπŸ‡¬πŸ‡§ Google2a00:1450:4009::/48
PTRyulhrs-in-f27.1e100.net
A2a00:1450:4009:c19::1aπŸ‡¬πŸ‡§ Google2a00:1450:4009::/48
PTRyulhrp-in-f26.1e100.net
A2a00:1450:4009:c19::1bπŸ‡¬πŸ‡§ Google2a00:1450:4009::/48
PTRyulhrp-in-f27.1e100.net
A172.217.76.26πŸ‡ΊπŸ‡Έ Google172.217.76.0/24
PTRyulhrp-in-f26.1e100.net
A172.217.76.27πŸ‡ΊπŸ‡Έ Google172.217.76.0/24
PTRyulhrp-in-f27.1e100.net
A192.178.223.26πŸ‡ΊπŸ‡Έ Google192.178.223.0/24
PTRyulhrs-in-f26.1e100.net
A192.178.223.27πŸ‡ΊπŸ‡Έ Google192.178.223.0/24
PTRyulhrs-in-f27.1e100.net
TXTv=spf1 a:www925.sakura.ne.jp include:_spf.google.com mx ~all
SOAmaster.dns.ne.jptech@sakura.ad.jp 2026-06-24 #21

com

Subdomains

Same first word

Similar names

DNS History

14 records (6 active, 8 former)

20162017201820192020202120222023202420252026NSmaster.dns.ne.jpns1.dns.ne.jpns2.dns.ne.jpMXsmtp.google.comalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comA219.94.128.1652403:3a00:101:9:219:94:128:165153.127.24.122401:2500:204:1110:153:127:24:1249.212.169.73
●NSmaster.dns.ne.jp2015-05-24 β†’ 2026-07-07 Β· 2 obs
● 2015-05-24 12:32:54
● 2026-07-07 21:59:10
●NSns1.dns.ne.jp2015-05-24 β†’ 2026-07-07 Β· 2 obs
● 2015-05-24 12:32:54
● 2026-07-07 21:59:10
●NSns2.dns.ne.jp2015-05-24 β†’ 2026-07-07 Β· 2 obs
● 2015-05-24 12:32:54
● 2026-07-07 21:59:10
β—‹MXalt1.aspmx.l.google.com2015-05-24 β†’ 2026-04-23 Β· 4 obs
● 2015-05-24 12:32:54
● 2026-04-23 06:56:56
β—‹ 2026-07-07 21:59:08
β—‹ 2026-07-07 21:59:10
β—‹MXalt2.aspmx.l.google.com2015-05-24 β†’ 2026-04-23 Β· 4 obs
● 2015-05-24 12:32:54
● 2026-04-23 06:56:56
β—‹ 2026-07-07 21:59:08
β—‹ 2026-07-07 21:59:10
β—‹MXaspmx.l.google.com2015-05-24 β†’ 2026-04-23 Β· 4 obs
● 2015-05-24 12:32:54
● 2026-04-23 06:56:56
β—‹ 2026-07-07 21:59:08
β—‹ 2026-07-07 21:59:10
β—‹MXaspmx2.googlemail.com2015-05-24 β†’ 2026-04-23 Β· 4 obs
● 2015-05-24 12:32:54
● 2026-04-23 06:56:56
β—‹ 2026-07-07 21:59:08
β—‹ 2026-07-07 21:59:10
β—‹MXaspmx3.googlemail.com2015-05-24 β†’ 2026-04-23 Β· 4 obs
● 2015-05-24 12:32:54
● 2026-04-23 06:56:56
β—‹ 2026-07-07 21:59:08
β—‹ 2026-07-07 21:59:10
●MXsmtp.google.com2026-07-07 β†’ 2026-07-07 Β· 3 obs
β—‹ 2026-04-23 06:56:56
● 2026-07-07 21:59:08
● 2026-07-07 21:59:10
β—‹A153.127.24.122026-02-15 β†’ 2026-04-23 Β· 5 obs
β—‹ 2017-04-24 10:16:38
● 2026-02-15 19:24:54
● 2026-04-23 06:56:56
β—‹ 2026-07-07 21:59:08
β—‹ 2026-07-07 21:59:10
●A219.94.128.1652026-07-07 β†’ 2026-07-07 Β· 3 obs
β—‹ 2026-04-23 06:56:56
● 2026-07-07 21:59:08
● 2026-07-07 21:59:10
β—‹A2401:2500:204:1110:153:127:24:122026-02-15 β†’ 2026-04-23 Β· 5 obs
β—‹ 2017-04-24 10:16:38
● 2026-02-15 19:24:54
● 2026-04-23 06:56:56
β—‹ 2026-07-07 21:59:08
β—‹ 2026-07-07 21:59:10
●A2403:3a00:101:9:219:94:128:1652026-07-07 β†’ 2026-07-07 Β· 3 obs
β—‹ 2026-04-23 06:56:56
● 2026-07-07 21:59:08
● 2026-07-07 21:59:10
β—‹A49.212.169.732015-05-24 β†’ 2017-04-24 Β· 4 obs
● 2015-05-24 12:32:54
● 2017-04-24 10:16:38
β—‹ 2026-02-15 19:24:54
β—‹ 2026-07-07 21:59:10

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
digiper.comns1.dns.ne.jp, ns2.dns.ne.jp-

βœ… Authoritative Response

Server:133.167.21.1

NS records: ns1.dns.ne.jp, ns2.dns.ne.jp

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for digiper.com (unsigned zone)

⏱️ Timing

Total: 1048ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1219.94.128.165
AAAA12403:3a00:101:9:219:94:128:165
NS2ns1.dns.ne.jp, ns2.dns.ne.jp
MX1smtp.google.com (pri: 10)
TXT1v=spf1 a:www925.sakura.ne.jp include:_sp
SOA1master.dns.ne.jp tech.sakura.ad.jp

Analysis

Hierarchy

The domain digiper.com is a parent of digimail.digiper.com, www.digiper.com, ns.digiper.com and users.digiper.com.

IP Addresses

digiper.com has two IP addresses: 219.94.128.165 and 2403:3a00:101:9:219:94:128:165

Two other host names, along with ch-2.info, farmstay-tierra.sakura.ne.jp and mabifes.com, also share IP numbers with digiper.com.

Name Servers

digiper.com carries NS records delegating to master.dns.ne.jp, ns1.dns.ne.jp and ns2.dns.ne.jp.

At least some of digiper.com's name servers are shared with other domains, for example green-eco.info, yu-taka.com, kushiro.me and two more.

master.dns.ne.jp points to 210.224.172.18; ns1.dns.ne.jp points to 61.211.236.1; ns2.dns.ne.jp points to 133.167.21.1 β€” each hostname maps to exactly one IP address.

Mail Servers

The sole mail server for digiper.com is smtp.google.com.

Among the domains sharing a mail server setup with digiper.com are writeitoff.com.au, software-analytics.com, gonthier.com and two others.

There is at least a partial MX overlap between digiper.com and other domains, including linuxsupportservices.net, upsh.com, vanlierop.com and two others.

These mail servers often co-occur with the mail servers aspmx.l.google.com.

With 8 IP addresses total, smtp.google.com resolves to 172.217.76.26, 172.217.76.27, 192.178.223.26 and 5 others.