standardbricks.com - dns.ninja
standardbricks.com
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=1784441797 | ||||||
Previously MX for
standardbricks.com |
Same first word
standardbricks.com |
DNS History
18 records (10 active, 8 former)
●NSns1.trafficpullz.co.in2017-03-21 → 2026-07-19 · 5 obs
● 2017-03-21 16:13:50
○ 2020-02-03 15:44:32
● 2026-02-18 16:31:18
● 2026-07-19 06:34:50
●NSns101.trafficpullz.net2026-02-18 → 2026-07-19 · 3 obs
● 2026-02-18 16:31:18
● 2026-07-19 06:34:50
●NSns102.trafficpullz.net2026-02-18 → 2026-07-19 · 3 obs
● 2026-02-18 16:31:18
● 2026-07-19 06:34:50
●NSns2.trafficpullz.co.in2017-03-21 → 2026-07-19 · 5 obs
● 2017-03-21 16:13:50
○ 2020-02-03 15:44:32
● 2026-02-18 16:31:18
● 2026-07-19 06:34:50
○NSns21.websitewelcome.com2015-08-20 → 2016-03-19 · 4 obs
● 2016-03-19 03:57:04
○ 2016-07-14 06:08:26
○ 2026-07-19 06:34:50
○NSns22.websitewelcome.com2015-08-20 → 2016-03-19 · 4 obs
● 2016-03-19 03:57:04
○ 2016-07-14 06:08:26
○ 2026-07-19 06:34:50
○NSns81.trafficpullz.com2020-02-03 → 2020-02-03 · 4 obs
● 2020-02-03 15:44:32
○ 2026-02-18 16:31:18
○ 2026-07-19 06:34:50
○NSns82.trafficpullz.com2020-02-03 → 2020-02-03 · 4 obs
● 2020-02-03 15:44:32
○ 2026-02-18 16:31:18
○ 2026-07-19 06:34:50
●MXalt1.aspmx.l.google.com2020-02-03 → 2026-07-19 · 3 obs
● 2020-02-03 15:44:32
● 2026-07-19 06:34:50
●MXalt2.aspmx.l.google.com2020-02-03 → 2026-07-19 · 3 obs
● 2020-02-03 15:44:32
● 2026-07-19 06:34:50
●MXalt3.aspmx.l.google.com2020-02-03 → 2026-07-19 · 3 obs
● 2020-02-03 15:44:32
● 2026-07-19 06:34:50
●MXalt4.aspmx.l.google.com2020-02-03 → 2026-07-19 · 3 obs
● 2020-02-03 15:44:32
● 2026-07-19 06:34:50
●MXaspmx.l.google.com2020-02-03 → 2026-07-19 · 3 obs
● 2020-02-03 15:44:32
● 2026-07-19 06:34:50
○MXstandardbricks.com2015-08-20 → 2017-03-21 · 6 obs
● 2016-03-19 03:57:04
○ 2016-07-14 06:08:26
● 2017-03-21 16:13:50
○ 2020-02-03 15:44:32
○ 2026-07-19 06:34:50
●A103.101.59.632026-02-18 → 2026-07-19 · 3 obs
● 2026-02-18 16:31:18
● 2026-07-19 06:34:50
○A103.195.185.1152017-03-21 → 2017-03-21 · 4 obs
● 2017-03-21 16:13:50
○ 2020-02-03 15:44:32
○ 2026-07-19 06:34:50
○A182.18.169.312020-02-03 → 2020-02-03 · 4 obs
● 2020-02-03 15:44:32
○ 2026-02-18 16:31:18
○ 2026-07-19 06:34:50
○A192.185.79.1062015-08-20 → 2016-03-19 · 4 obs
● 2016-03-19 03:57:04
○ 2016-07-14 06:08:26
○ 2026-07-19 06:34:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| standardbricks.com | ns1.trafficpullz.co.in, ns2.trafficpullz.co.in | - |
✅ Authoritative Response
Server:103.101.59.63
NS records: ns1.trafficpullz.co.in, ns2.trafficpullz.co.in
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for standardbricks.com (unsigned zone)
⏱️ Timing
Total: 2355ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 103.101.59.63 |
| NS | 2 | ns101.trafficpullz.net, ns102.trafficpullz.net |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=udHgBFi4IylZ7py, v=spf1 +a +mx +ip4:103.101.59.63 +includ |
| SOA | 1 | ns101.trafficpullz.net trafficpullz.gmai |
Analysis
IP Addresses
standardbricks.com points to a single IP number: 103.101.59.63.
Additional host names — pambaheritage.com, ns101.trafficpullz.net, arml.in and two others — share IP numbers with standardbricks.com.
Name Servers
standardbricks.com has four authoritative name servers: ns101.trafficpullz.net, ns102.trafficpullz.net, ns1.trafficpullz.co.in and ns2.trafficpullz.co.in.
There is at least partial name server overlap between standardbricks.com and other domains — d2lpharma.com, sanyog.com, cosmopoltravel.com and two more among them.
These name servers regularly appear alongside ns1.103-101-59-63.cprapid.com, ns2.103-101-59-63.cprapid.com, ns91.trafficpullz.com and 3 other name servers in NS record sets.
ns101.trafficpullz.net, ns102.trafficpullz.net, ns1.trafficpullz.co.in and ns2.trafficpullz.co.in each point to one IP number, which is 103.101.59.63 in every case.
The host names ns101.trafficpullz.net, ns102.trafficpullz.net, ns1.trafficpullz.co.in and ns2.trafficpullz.co.in all point to 103.101.59.63.
Mail Servers
Five mail servers handle standardbricks.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
standardbricks.com shares mail servers — at least in part — with other domains, including oldcolonymontessori.org, hyowon.asia, ns500734.ns500734.ns500699.ns500693.ns500693.ns500699.ns500588.ns500693.ns500683.ns500588.ns500588.ns500632.ns500612.dtrkdll.com and two others.
These mail servers are frequently paired with the mail servers alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com resolves to two addresses: 142.251.16.27 and 2607:f8b0:4004:c1f::1b.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1a.