problematic.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

problematic.com

DNSSEC⚠️ Not signed
A50.31.210.85🇺🇸 SERVERCENTRAL50.31.208.0/20
PTRunknown.servercentral.net
NSdns109.a.register.com ⭐ ⚠️ Not in parent delegation
A216.21.231.109🇺🇸 Jacksonville216.21.231.0/24 5335 Gate Parkway Jacksonville FL 32256 United States
PTRdns109.a.register.com
NSdns082.d.register.com ⚠️ Not in parent delegation
A216.21.236.82🇺🇸 Jacksonville216.21.236.0/24 5335 Gate Parkway Jacksonville FL 32256 United States
PTRdns082.d.register.com
NSdns092.c.register.com ⚠️ Not in parent delegation
A216.21.235.92🇺🇸 Jacksonville216.21.234.0/23 NF ATL SUBNETS
PTRdns092.c.register.com
NSdns1.register.com ⚠️ Not in zone NS records
A162.159.27.248Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSdns196.b.register.com ⚠️ Not in parent delegation
A216.21.232.196🇺🇸 Jacksonville216.21.232.0/24 5335 Gate Parkway Jacksonville FL 32256 United States
PTRdns196.b.register.com
NSdns2.register.com ⚠️ Not in zone NS records
A162.159.26.197Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
SOAdns109.a.register.comroot@register.com 2010-07-02 #2

com

Same first word

Similar names

Previous names

Next names

DNS History

8 records (7 active, 1 former)

20162017201820192020202120222023202420252026NSdns082.d.register.comdns092.c.register.comdns1.register.comdns109.a.register.comdns196.b.register.comdns2.register.comMXp.webcom.ctmail.comA50.31.210.85
●NSdns082.d.register.com2015-05-12 → 2026-10-07 · 2 obs
● 2015-05-12 22:03:44
● 2026-10-07 03:11:36
●NSdns092.c.register.com2015-05-12 → 2026-10-07 · 2 obs
● 2015-05-12 22:03:44
● 2026-10-07 03:11:36
●NSdns1.register.com2026-08-29 → 2026-10-07 · 3 obs
○ 2015-05-12 22:03:44
● 2026-08-29 11:58:54
● 2026-10-07 03:11:36
●NSdns109.a.register.com2015-05-12 → 2026-10-07 · 2 obs
● 2015-05-12 22:03:44
● 2026-10-07 03:11:36
●NSdns196.b.register.com2015-05-12 → 2026-10-07 · 2 obs
● 2015-05-12 22:03:44
● 2026-10-07 03:11:36
●NSdns2.register.com2026-08-29 → 2026-10-07 · 3 obs
○ 2015-05-12 22:03:44
● 2026-08-29 11:58:54
● 2026-10-07 03:11:36
○MXp.webcom.ctmail.com2017-03-27 → 2017-03-27 · 3 obs
● 2017-03-27 18:57:36
○ 2026-08-29 11:58:54
○ 2026-10-07 03:11:36
●A50.31.210.852015-05-12 → 2026-10-07 · 2 obs
● 2015-05-12 22:03:44
● 2026-10-07 03:11:36

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
problematic.comdns1.register.com, dns2.register.com2 records

✅ Authoritative Response

Server:162.159.27.248

NS records: dns1.register.com, dns2.register.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for problematic.com (unsigned zone)

⏱️ Timing

Total: 304ms | Queries: -

📄 Records

TypeCountSample Data
A150.31.210.85
NS4dns109.a.register.com, dns092.c.register.com...
SOA1dns109.a.register.com root.register.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns1.register.com, dns2.register.com)

Analysis

IP Addresses

problematic.com points to a single IP number: 50.31.210.85.

Additional host names — frmail.com, tennismail.com, gunpoint.com and two others — share IP numbers with problematic.com.

Name Servers

DNS for problematic.com is handled by 6 name servers: dns1.register.com, dns2.register.com, dns109.a.register.com and 3 others.

problematic.com has at least partial name server overlap with other domains, such as humanrightsforafghanistan.org, kotasodeals.com, mekongcharmcruiseandtravel.com and two others.

dns083.d.register.com, dns082.d.register.com and dns196.b.register.com — plus 7 other name servers — are commonly paired with these name servers.

Host names pointing to a single IP address:

dns1.register.com directs to 162.159.27.248.

dns2.register.com directs to 162.159.26.197.

dns109.a.register.com directs to 216.21.231.109.

dns196.b.register.com directs to 216.21.232.196.

dns092.c.register.com directs to 216.21.235.92.

dns082.d.register.com directs to 216.21.236.82.