fastalert.jp - robtex.com
fastalert.jp
jp
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | z.dns.jp ⭐ | ||||||
| NS | a.dns.jp | ||||||
| NS | b.dns.jp | ||||||
| NS | c.dns.jp | ||||||
| NS | d.dns.jp | ||||||
| NS | e.dns.jp | ||||||
| NS | f.dns.jp | ||||||
| NS | g.dns.jp | ||||||
| NS | h.dns.jp | ||||||
| SOA | z.dns.jproot@dns.jp serial=1773558003 | ||||||
Same first word
Similar names
DNS History
6 records (6 active, 0 former)
●NSns-1037.awsdns-01.org2026-02-24 → 2026-03-23 · 2 obs
● 2026-03-23 18:11:02
●NSns-1611.awsdns-09.co.uk2026-02-24 → 2026-03-23 · 2 obs
● 2026-03-23 18:11:02
●NSns-613.awsdns-12.net2026-02-24 → 2026-03-23 · 2 obs
● 2026-03-23 18:11:02
●NSns-8.awsdns-01.com2026-02-24 → 2026-03-23 · 2 obs
● 2026-03-23 18:11:02
●MXinbound-smtp.us-east-1.amazonaws.com2026-02-24 → 2026-03-23 · 2 obs
● 2026-03-23 18:11:02
●A34.111.141.2252026-02-24 → 2026-03-23 · 2 obs
● 2026-03-23 18:11:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp... | - |
| fastalert.jp | ns-1037.awsdns-01.org, ns-1611.awsdns-09.co.uk, ns-8.awsdns-01.com, ns-613.awsdns-12.net | - |
✅ Authoritative Response
Server:205.251.192.8
NS records: ns-1037.awsdns-01.org, ns-1611.awsdns-09.co.uk, ns-8.awsdns-01.com, ns-613.awsdns-12.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fastalert.jp (unsigned zone)
⏱️ Timing
Total: 854ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 34.111.141.225 |
| NS | 4 | ns-1037.awsdns-01.org, ns-1611.awsdns-09.co.uk... |
| MX | 1 | inbound-smtp.us-east-1.amazonaws.com (pr |
| TXT | 7 | facebook-domain-verification=1okpjvi43j1, google-site-verification=618nDCgR3qNMCfH... |
| SOA | 1 | ns-1611.awsdns-09.co.uk awsdns-hostmaste |
Analysis
IP Addresses
fastalert.jp points to a single IP number: 34.111.141.225.
Other host names, for instance mail.iwatoyouchien.com, skyinc.jp, rikiman.com, ruxx.net and abank.co.jp share IP numbers with fastalert.jp.
Name Servers
fastalert.jp is delegated to four name servers: ns-8.awsdns-01.com, ns-613.awsdns-12.net, ns-1037.awsdns-01.org and ns-1611.awsdns-09.co.uk.
fastalert.jp shares name servers with other domains at least partially, for instance medusaserver.com, prod2.ap.dynp.cloud1.vv1865.com, dev.idgmc.org, d2p138f5ea2su5.cloudfront.net and creddogroup.com.
these name servers are often used with ns-269.awsdns-33.com, ns-1019.awsdns-63.net and ns-1418.awsdns-49.org.
Host names with two IP numbers:
ns-8.awsdns-01.com resolves to 2600:9000:5300:800::1 and 205.251.192.8.
ns-613.awsdns-12.net resolves to 2600:9000:5302:6500::1 and 205.251.194.101.
ns-1037.awsdns-01.org resolves to 2600:9000:5304:d00::1 and 205.251.196.13.
ns-1611.awsdns-09.co.uk resolves to 2600:9000:5306:4b00::1 and 205.251.198.75.
Mail Servers
The mail server for fastalert.jp is inbound-smtp.us-east-1.amazonaws.com.
fastalert.jp shares the same mail server setup as other domains, including tttri.slack.com, btcohen.com, mckinsey-client-cap.slack.com, khronosdevs.slack.com and oceanharvest.slack.com.
fastalert.jp shares some mail servers with other domains, including gerberlife.atlassian.net, zg-cte.atlassian.net, thewinningkey.com, mytollproject.atlassian.net and tkco.atlassian.net.
These mail servers are often used with the mail servers inbound-smtp.us-west-2.amazonaws.com.
Host name inbound-smtp.us-east-1.amazonaws.com points to five IP numbers: 3.211.210.226, 44.206.9.87, 44.210.166.32, 54.164.173.191 and 54.197.5.236.