field360.in - robtex.com
field360.in
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns.trs-dns.com ⭐ | ||||||
| NS | ns1.registry.in | ||||||
| NS | ns2.registry.in | ||||||
| NS | ns3.registry.in | ||||||
| NS | ns4.registry.in | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1782930666 | ||||||
Same first word
field360.in |
DNS History
8 records (8 active, 0 former)
●NSns31.domaincontrol.com2026-06-02 → 2026-07-01 · 2 obs
● 2026-07-01 18:40:12
●NSns32.domaincontrol.com2026-06-02 → 2026-07-01 · 2 obs
● 2026-07-01 18:40:12
●MXalt1.aspmx.l.google.com2026-06-02 → 2026-07-01 · 2 obs
● 2026-07-01 18:40:12
●MXalt2.aspmx.l.google.com2026-06-02 → 2026-07-01 · 2 obs
● 2026-07-01 18:40:12
●MXalt3.aspmx.l.google.com2026-06-02 → 2026-07-01 · 2 obs
● 2026-07-01 18:40:12
●MXalt4.aspmx.l.google.com2026-06-02 → 2026-07-01 · 2 obs
● 2026-07-01 18:40:12
●MXaspmx.l.google.com2026-06-02 → 2026-07-01 · 2 obs
● 2026-07-01 18:40:12
●A34.131.138.1402026-06-02 → 2026-07-01 · 2 obs
● 2026-07-01 18:40:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns1.registry.in, ns3.registry.in, ns2.registry.in, ns4.registry.in | - |
| field360.in | ns31.domaincontrol.com, ns32.domaincontrol.com | - |
✅ Authoritative Response
Server:173.201.73.16
NS records: ns31.domaincontrol.com, ns32.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for field360.in (unsigned zone)
⏱️ Timing
Total: 484ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 34.131.138.140 |
| NS | 2 | ns31.domaincontrol.com, ns32.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 4 | facebook-domain-verification=e0wl2pl50r3, google-site-verification=kNJ9BnqU9JYOWwy... |
| SOA | 1 | ns31.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
field360.in resolves to just one IP address, 34.131.138.140.
Name Servers
The NS records for field360.in delegate to ns31.domaincontrol.com and ns32.domaincontrol.com.
field360.in shares its NS records with other domains, for example paragonplacements.com, helpfulbeauty.com, saltlakemaryj.com and two others.
field360.in shares at least some of its name servers with other domains, such as advantaseeds.com and tricore.ca.
ns31.domaincontrol.com resolves to 97.74.105.16 and 2603:5:2191::10. Likewise, ns32.domaincontrol.com resolves to 173.201.73.16 and 2603:5:2291::10 — two IP addresses apiece.
Mail Servers
Mail for field360.in is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between field360.in and other domains, including kydon.gr, ns500731.ns500731.ns500754.ns500754.ns500671.ns500704.ns500688.ns500704.ns500678.ns500291.ns500678.ns500653.ns500131.lustychickser.com, ns500742.ns500731.ns500731.ns500671.ns500704.ns500742.ns500704.ns500742.ns500704.ns500704.ns500671.ns500678.ns500678.ns500688.ns500671.ns500649.lustychickser.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
The A records for aspmx.l.google.com return 172.253.115.26 and 2607:f8b0:4004:c08::1a.
The A records for alt1.aspmx.l.google.com return 108.177.123.26 and 2800:3f0:4003:c0f::1a.
The A records for alt2.aspmx.l.google.com return 172.253.116.26 and 2a00:1450:400b:c02::1a.
The A records for alt3.aspmx.l.google.com return 192.178.223.27 and 2a00:1450:4009:c0f::1b.
The A records for alt4.aspmx.l.google.com return 172.253.157.26 and 2a00:1450:400c:c23::1a.