britama.com - robtex.com
britama.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | dns1.indosite.co.id ⚠️ Not in zone NS records | ||||||
| A | 103.30.147.9🇮🇩 JOGJACAMP-AS-ID103.30.147.0/24 Proxy-registered route object | ||||||
| PTR | ns1.liqu.id | ||||||
| NS | dns2.indosite.co.id ⚠️ Not in zone NS records | ||||||
| A | 202.52.146.225🇮🇩 GMEDIA-AS-ID202.52.146.0/24 Proxy-registered route object | ||||||
| PTR | ns2.liqu.id | ||||||
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.netnstld@verisign-grs.com serial=1778651676 | ||||||
Previously MX for
britama.com |
Same first word
britama.com |
Similar names
DNS History
9 records (2 active, 7 former)
●NSdns1.indosite.co.id2026-04-08 → 2026-05-13 · 3 obs
○ 2017-02-12 02:41:36
● 2026-04-08 18:55:48
● 2026-05-13 05:58:44
● 2026-04-08 18:55:48
● 2026-05-13 05:58:44
●NSdns2.indosite.co.id2026-04-08 → 2026-05-13 · 3 obs
○ 2017-02-12 02:41:36
● 2026-04-08 18:55:48
● 2026-05-13 05:58:44
● 2026-04-08 18:55:48
● 2026-05-13 05:58:44
○NSns1.britama.net2015-06-20 → 2016-01-23 · 5 obs
○ 2008-03-16 15:13:58
● 2015-06-20 01:53:54
● 2016-01-23 10:11:16
○ 2016-06-28 15:19:08
○ 2026-05-13 05:58:44
● 2015-06-20 01:53:54
● 2016-01-23 10:11:16
○ 2016-06-28 15:19:08
○ 2026-05-13 05:58:44
○NSns1.britama.org2016-06-28 → 2017-02-12 · 5 obs
○ 2016-01-23 10:11:16
● 2016-06-28 15:19:08
● 2017-02-12 02:41:36
○ 2026-04-08 18:55:48
○ 2026-05-13 05:58:44
● 2016-06-28 15:19:08
● 2017-02-12 02:41:36
○ 2026-04-08 18:55:48
○ 2026-05-13 05:58:44
○NSns2.britama.net2015-06-20 → 2016-01-23 · 5 obs
○ 2008-03-16 15:13:58
● 2015-06-20 01:53:54
● 2016-01-23 10:11:16
○ 2016-06-28 15:19:08
○ 2026-05-13 05:58:44
● 2015-06-20 01:53:54
● 2016-01-23 10:11:16
○ 2016-06-28 15:19:08
○ 2026-05-13 05:58:44
○NSns2.britama.org2016-06-28 → 2017-02-12 · 5 obs
○ 2016-01-23 10:11:16
● 2016-06-28 15:19:08
● 2017-02-12 02:41:36
○ 2026-04-08 18:55:48
○ 2026-05-13 05:58:44
● 2016-06-28 15:19:08
● 2017-02-12 02:41:36
○ 2026-04-08 18:55:48
○ 2026-05-13 05:58:44
○MXbritama.com2015-06-20 → 2017-02-12 · 5 obs
○ 2008-03-16 15:13:58
● 2015-06-20 01:53:54
● 2017-02-12 02:41:36
○ 2026-04-08 18:55:48
○ 2026-05-13 05:58:44
● 2015-06-20 01:53:54
● 2017-02-12 02:41:36
○ 2026-04-08 18:55:48
○ 2026-05-13 05:58:44
○A192.254.134.92016-06-28 → 2017-02-12 · 5 obs
○ 2016-01-23 10:11:16
● 2016-06-28 15:19:08
● 2017-02-12 02:41:36
○ 2026-04-08 18:55:48
○ 2026-05-13 05:58:44
● 2016-06-28 15:19:08
● 2017-02-12 02:41:36
○ 2026-04-08 18:55:48
○ 2026-05-13 05:58:44
○A192.254.211.2462015-06-20 → 2016-01-23 · 5 obs
○ 2008-03-16 15:13:58
● 2015-06-20 01:53:54
● 2016-01-23 10:11:16
○ 2016-06-28 15:19:08
○ 2026-05-13 05:58:44
● 2015-06-20 01:53:54
● 2016-01-23 10:11:16
○ 2016-06-28 15:19:08
○ 2026-05-13 05:58:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| britama.com | dns1.indosite.co.id, dns2.indosite.co.id | - |
✅ Authoritative Response
Server:202.52.146.225
NS records: dns1.indosite.co.id, dns2.indosite.co.id
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for britama.com (unsigned zone)
⏱️ Timing
Total: 1295ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
britama.com's delegation is to two name servers dns1.indosite.co.id and dns2.indosite.co.id.
britama.com shares name servers with other domains at least partially, for example marketspace.id.
These name servers are commonly used alongside dns3.indosite.co.id and dns4.indosite.co.id.
Host names with a single IP:
dns1.indosite.co.id resolves to 103.30.147.9.
dns2.indosite.co.id resolves to 202.52.146.225.