beingdaddy.com - dns.ninja

beingdaddy.com

com

WOT: SAFE (62/100)

Previously MX for

Same first word

DNS History

12 records (4 active, 8 former)

200920112013201520172019202120232025NSns3.afternic.comns4.afternic.comns-1426.awsdns-50.orgns-149.awsdns-18.comns-1591.awsdns-06.co.ukns-833.awsdns-40.netMX.beingdaddy.comA13.248.169.4876.223.54.146149.47.18.13063.247.141.136
NSns-1426.awsdns-50.org2015-06-23 → 2020-03-27 · 5 obs
○ 2008-03-20 10:56:54
● 2015-06-23 19:29:54
● 2020-03-27 04:11:48
○ 2026-03-17 05:43:34
○ 2026-07-12 03:24:10
NSns-149.awsdns-18.com2015-06-23 → 2020-03-27 · 5 obs
○ 2008-03-20 10:56:54
● 2015-06-23 19:29:54
● 2020-03-27 04:11:48
○ 2026-03-17 05:43:34
○ 2026-07-12 03:24:10
NSns-1591.awsdns-06.co.uk2015-06-23 → 2020-03-27 · 5 obs
○ 2008-03-20 10:56:54
● 2015-06-23 19:29:54
● 2020-03-27 04:11:48
○ 2026-03-17 05:43:34
○ 2026-07-12 03:24:10
NSns-833.awsdns-40.net2015-06-23 → 2020-03-27 · 5 obs
○ 2008-03-20 10:56:54
● 2015-06-23 19:29:54
● 2020-03-27 04:11:48
○ 2026-03-17 05:43:34
○ 2026-07-12 03:24:10
NSns3.afternic.com2026-03-17 → 2026-07-12 · 3 obs
○ 2020-03-27 04:11:48
● 2026-03-17 05:43:34
● 2026-07-12 03:24:10
NSns4.afternic.com2026-03-17 → 2026-07-12 · 3 obs
○ 2020-03-27 04:11:48
● 2026-03-17 05:43:34
● 2026-07-12 03:24:10
MX.2026-03-17 → 2026-07-12 · 2 obs
○ 2026-03-17 05:43:34
○ 2026-07-12 03:24:10
MXbeingdaddy.com2015-06-23 → 2020-03-27 · 5 obs
○ 2008-03-20 10:56:54
● 2015-06-23 19:29:54
● 2020-03-27 04:11:48
○ 2026-03-17 05:43:34
○ 2026-07-12 03:24:10
A13.248.169.482026-03-17 → 2026-07-12 · 3 obs
○ 2020-03-27 04:11:48
● 2026-03-17 05:43:34
● 2026-07-12 03:24:10
A149.47.18.1302015-06-23 → 2020-03-27 · 5 obs
○ 2008-03-20 10:56:54
● 2015-06-23 19:29:54
● 2020-03-27 04:11:48
○ 2026-03-17 05:43:34
○ 2026-07-12 03:24:10
A63.247.141.1362008-03-20 → 2008-03-20 · 3 obs
● 2008-03-20 10:56:54
○ 2015-06-23 19:29:54
○ 2026-07-12 03:24:10
A76.223.54.1462026-03-17 → 2026-07-12 · 3 obs
○ 2020-03-27 04:11:48
● 2026-03-17 05:43:34
● 2026-07-12 03:24:10

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coml.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...-
beingdaddy.comns3.afternic.com, ns4.afternic.com2 records

✅ Authoritative Response

Server:97.74.98.65

NS records: ns3.afternic.com, ns4.afternic.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for beingdaddy.com (unsigned zone)

⏱️ Timing

Total: 2231ms | Queries: -

📄 Records

TypeCountSample Data
A213.248.169.48, 76.223.54.146
NS2ns3.afternic.com, ns4.afternic.com
MX1. (pri: 0)
TXT1v=spf1 -all
SOA1ns3.afternic.com dns.jomax.net

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns3.afternic.com, ns4.afternic.com)

Analysis

IP Addresses

beingdaddy.com points to the IP addresses 13.248.169.48 and 76.223.54.146

Additional host names — ukrainecrypto.xyz, oskemen.net, shisenshop.xyz and two others — share IP numbers with beingdaddy.com.

Name Servers

beingdaddy.com has two authoritative name servers — ns3.afternic.com and ns4.afternic.com.

beingdaddy.com shares its name server setup with other domains, including ratee.com, ustrt.com, www.regexadvice.com and two others.

The name servers of beingdaddy.com overlap at least partially with those of other domains — among them insta.capital, spirit.digital, towber.com and two more.

These name servers commonly appear in combination with the name servers verification-frsgyqgb387khmr9jzuunx.ns101.verify.hn.

Both ns3.afternic.com and ns4.afternic.com have a single IP address each — ns3.afternic.com resolves to 97.74.98.65 while ns4.afternic.com resolves to 173.201.66.65.