sf-sync.api.mx2.dev - dns.ninja
sf-sync.api.mx2.dev
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.224.30.60🇺🇸 Amazon3.224.0.0/12 EC2 IAD prefix | ||||||
| PTR | ec2-3-224-30-60.compute-1.amazonaws.com | ||||||
| A | 18.214.177.30🇺🇸 Amazon18.208.0.0/13 EC2 IAD prefix | ||||||
| A | 100.48.248.94🇺🇸 Amazon100.48.0.0/12 EC2 IAD prefix | ||||||
api.mx2.dev
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns-361.awsdns-45.com ⭐ | ||||||
| NS | ns-1107.awsdns-10.org | ||||||
| NS | ns-1683.awsdns-18.co.uk | ||||||
| NS | ns-770.awsdns-32.net | ||||||
| SOA | ns-361.awsdns-45.comawsdns-hostmaster@amazon.com serial=1 | ||||||
DNS History
9 records (3 active, 6 former)
●A100.48.248.942026-06-07 → 2026-06-07 · 3 obs
○ 2026-05-13 02:20:04
● 2026-06-07 04:29:42
● 2026-06-07 04:29:44
● 2026-06-07 04:29:42
● 2026-06-07 04:29:44
○A18.214.107.762026-05-13 → 2026-05-13 · 3 obs
● 2026-05-13 02:20:04
○ 2026-06-07 04:29:42
○ 2026-06-07 04:29:44
○ 2026-06-07 04:29:42
○ 2026-06-07 04:29:44
●A18.214.177.302026-06-07 → 2026-06-07 · 3 obs
○ 2026-05-13 02:20:04
● 2026-06-07 04:29:42
● 2026-06-07 04:29:44
● 2026-06-07 04:29:42
● 2026-06-07 04:29:44
○A23.21.139.82026-05-13 → 2026-06-07 · 2 obs
○ 2026-05-13 02:20:04
○ 2026-06-07 04:29:44
○ 2026-06-07 04:29:44
●A3.224.30.602026-06-07 → 2026-06-07 · 3 obs
○ 2026-05-13 02:20:04
● 2026-06-07 04:29:42
● 2026-06-07 04:29:44
● 2026-06-07 04:29:42
● 2026-06-07 04:29:44
○A3.229.178.1492026-05-13 → 2026-06-07 · 2 obs
○ 2026-05-13 02:20:04
○ 2026-06-07 04:29:44
○ 2026-06-07 04:29:44
○A34.228.211.302026-05-13 → 2026-05-13 · 3 obs
● 2026-05-13 02:20:04
○ 2026-06-07 04:29:42
○ 2026-06-07 04:29:44
○ 2026-06-07 04:29:42
○ 2026-06-07 04:29:44
○A35.169.253.2502026-05-13 → 2026-05-13 · 3 obs
● 2026-05-13 02:20:04
○ 2026-06-07 04:29:42
○ 2026-06-07 04:29:44
○ 2026-06-07 04:29:42
○ 2026-06-07 04:29:44
○A54.224.225.332026-05-13 → 2026-06-07 · 2 obs
○ 2026-05-13 02:20:04
○ 2026-06-07 04:29:44
○ 2026-06-07 04:29:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | - |
| mx2.dev | ns-114.awsdns-14.com, ns-1069.awsdns-05.org, ns-1780.awsdns-30.co.uk, ns-644.awsdns-16.net | - |
| api.mx2.dev | ns-1107.awsdns-10.org, ns-1683.awsdns-18.co.uk, ns-361.awsdns-45.com, ns-770.awsdns-32.net | - |
✅ Authoritative Response
Server:205.251.196.83
NS records: ns-1107.awsdns-10.org, ns-1683.awsdns-18.co.uk, ns-361.awsdns-45.com, ns-770.awsdns-32.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mx2.dev (unsigned zone)
⏱️ Timing
Total: 882ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 3 | 18.214.177.30, 100.48.248.94... |
Analysis
IP Addresses
sf-sync.api.mx2.dev directs to three IP numbers: 3.224.30.60, 18.214.177.30 and 100.48.248.94.
Other host names, such as ec2-18-214-177-30.compute-1.amazonaws.com, share IP numbers with sf-sync.api.mx2.dev.