bizzyblogger.com - robtex.com
bizzyblogger.com
| DNSSEC | β οΈ Not signed | ||||||
| A | 192.185.5.160πΊπΈ Jacksonville192.185.5.0/24 | ||||||
| PTR | gator4030.hostgator.com | ||||||
| NS | ns8059.hostgator.com β | ||||||
| A | 192.185.5.160πΊπΈ Jacksonville192.185.5.0/24 | ||||||
| PTR | gator4030.hostgator.com | ||||||
| NS | ns3641.hostgator.com | ||||||
| A | 192.185.5.160πΊπΈ Jacksonville192.185.5.0/24 | ||||||
| PTR | gator4030.hostgator.com | ||||||
| NS | ns3642.hostgator.com | ||||||
| A | 192.185.5.161πΊπΈ Jacksonville192.185.5.0/24 | ||||||
| PTR | ns8060.hostgator.com | ||||||
| MX | bizzyblogger.com β | ||||||
| A | 192.185.5.160πΊπΈ Jacksonville192.185.5.0/24 | ||||||
| PTR | gator4030.hostgator.com | ||||||
| TXT | v=spf1 +a +mx +ip4:192.185.4.41 ?all | ||||||
| SOA | ns8059.hostgator.comdnsadmin@gator4030.hostgator.com 2026-03-30 #0 | ||||||
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=1774920417 | ||||||
Subdomains
mkt.bizzyblogger.com |
DNS History
5 records (5 active, 0 former)
βNSns3641.hostgator.com2015-07-10 β 2026-03-31 Β· 2 obs
β 2026-03-31 01:41:52
βNSns3642.hostgator.com2015-07-10 β 2026-03-31 Β· 2 obs
β 2026-03-31 01:41:52
βNSns8059.hostgator.com2015-07-10 β 2026-03-31 Β· 2 obs
β 2026-03-31 01:41:52
βMXbizzyblogger.com2015-07-10 β 2026-03-31 Β· 2 obs
β 2026-03-31 01:41:52
βA192.185.5.1602015-07-10 β 2026-03-31 Β· 2 obs
β 2026-03-31 01:41:52
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, l.gtld-servers.net, d.gtld-servers.net, c.gtld-servers.net... | - |
| bizzyblogger.com | ns3641.hostgator.com, ns3642.hostgator.com | 2 records |
β Authoritative Response
Server:192.185.5.160
NS records: ns3641.hostgator.com, ns3642.hostgator.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for bizzyblogger.com (unsigned zone)
β±οΈ Timing
Total: 179ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 192.185.5.160 |
| NS | 2 | ns3641.hostgator.com, ns3642.hostgator.com |
| MX | 1 | bizzyblogger.com (pri: 0) |
| TXT | 1 | v=spf1 +a +mx +ip4:192.185.4.41 ?all |
| SOA | 1 | ns8059.hostgator.com dnsadmin.gator4030. |
π Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns3641.hostgator.com, ns3642.hostgator.com)
Analysis
Hierarchy
The parent of mkt.bizzyblogger.com is bizzyblogger.com.
IP Addresses
bizzyblogger.com points to a single IP number: 192.185.5.160.
Other host names, for instance mail.phylliszimblermiller.com, hurricanehoodoo.com, ns1.kingkutterattachments.com, ccperformance.com and mail.fictionmarketing.com share IP numbers with bizzyblogger.com.
Name Servers
The domain bizzyblogger.com is delegated to three name servers: ns3641.hostgator.com, ns3642.hostgator.com and ns8059.hostgator.com.
bizzyblogger.com shares name servers with other domains at least partially, for instance pexim.com, sumbersarana.com, clearflt.com, thebraidzone.com and insitucrm.com.
these name servers are commonly paired with ns8060.hostgator.com, hgns1.hostgator.com, hgns2.hostgator.com, ns1069.hostgator.com, ns1070.hostgator.com, ns3413.hostgator.com, ns3414.hostgator.com, ns3453.hostgator.com and ns3454.hostgator.com.
Host names with one IP number:
The host name ns3641.hostgator.com points to 192.185.5.160.
The host name ns3642.hostgator.com points to 192.185.5.161.
The host name ns8059.hostgator.com points to 192.185.5.160.
Host names that point to 192.185.5.160: ns3641.hostgator.com and ns8059.hostgator.com.
Mail Servers
A single mail server handles bizzyblogger.com and bizzyblogger.com.
Host name bizzyblogger.com resolves to IP 192.185.5.160.