chiefarchitectblog.com - robtex.com
chiefarchitectblog.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=1778649826 | ||||||
Subdomains
www.chiefarchitectblog.com |
Same first word
chiefarchitectblog.com |
DNS History
5 records (5 active, 0 former)
βNSns-1418.awsdns-49.org2017-05-08 β 2026-05-13 Β· 2 obs
β 2026-05-13 05:32:38
βNSns-172.awsdns-21.com2017-05-08 β 2026-05-13 Β· 2 obs
β 2026-05-13 05:32:38
βNSns-2004.awsdns-58.co.uk2017-05-08 β 2026-05-13 Β· 2 obs
β 2026-05-13 05:32:38
βNSns-999.awsdns-60.net2017-05-08 β 2026-05-13 Β· 2 obs
β 2026-05-13 05:32:38
βA52.10.103.622017-05-08 β 2026-05-13 Β· 2 obs
β 2026-05-13 05:32:38
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, a.gtld-servers.net, c.gtld-servers.net, e.gtld-servers.net... | - |
| chiefarchitectblog.com | ns-172.awsdns-21.com, ns-999.awsdns-60.net, ns-2004.awsdns-58.co.uk, ns-1418.awsdns-49.org | 2 records |
β Authoritative Response
Server:205.251.192.172
NS records: ns-172.awsdns-21.com, ns-999.awsdns-60.net, ns-2004.awsdns-58.co.uk, ns-1418.awsdns-49.org
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for chiefarchitectblog.com (unsigned zone)
β±οΈ Timing
Total: 1049ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.10.103.62 |
| NS | 4 | ns-1418.awsdns-49.org, ns-172.awsdns-21.com... |
| TXT | 1 | google-site-verification=ndzb5YzkP8nM5j0 |
| SOA | 1 | ns-999.awsdns-60.net awsdns-hostmaster.a |
π Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-172.awsdns-21.com, ns-172.awsdns-21.com)
Analysis
Hierarchy
The parent of www.chiefarchitectblog.com is chiefarchitectblog.com.
IP Addresses
chiefarchitectblog.com points to a single IP number: 52.10.103.62.
Other host names, for instance ec2-52-10-103-62.us-west-2.compute.amazonaws.com and www.chiefarchitectblog.com, share IP numbers with chiefarchitectblog.com.
Name Servers
chiefarchitectblog.com is delegated to four name servers: ns-172.awsdns-21.com, ns-999.awsdns-60.net, ns-1418.awsdns-49.org and ns-2004.awsdns-58.co.uk.
chiefarchitectblog.com shares name servers with other domains at least partially, for instance d1zoxx18rz7gu5.cloudfront.net, browser-session.com, edpl.us, shimano.nl and 5.43.225.130.in-addr.arpa.
These name servers are commonly used with ns-1947.awsdns-51.co.uk, ns-293.awsdns-36.com, ns-789.awsdns-34.net, ns-87.awsdns-10.com, ns-1070.awsdns-05.org and ns-1601.awsdns-08.co.uk.
Host names with two IP numbers:
ns-172.awsdns-21.com resolves to 2600:9000:5300:ac00::1 and 205.251.192.172.
ns-999.awsdns-60.net resolves to 2600:9000:5303:e700::1 and 205.251.195.231.
ns-1418.awsdns-49.org resolves to 2600:9000:5305:8a00::1 and 205.251.197.138.
ns-2004.awsdns-58.co.uk resolves to 2600:9000:5307:d400::1 and 205.251.199.212.