problematically.com - dns.ninja

problematically.com

com

Subdomains

Same first word

DNS History

12 records (4 active, 8 former)

20162017201820192020202120222023202420252026NSns1.afternic.comns2.afternic.combuy.internettraffic.comns1.undeveloped.comns2.undeveloped.comsell.internettraffic.comMXmx.problematically.comA13.248.169.4876.223.54.14652.58.78.1669.172.201.20880.240.129.10
β—‹NSbuy.internettraffic.com2015-06-24 β†’ 2015-06-24 Β· 3 obs
● 2015-06-24 05:15:04
β—‹ 2015-11-02 06:10:10
β—‹ 2026-07-04 07:29:58
●NSns1.afternic.com2026-04-06 β†’ 2026-07-04 Β· 3 obs
β—‹ 2017-04-20 00:22:36
● 2026-04-06 14:50:54
● 2026-07-04 07:29:58
β—‹NSns1.undeveloped.com2015-11-02 β†’ 2017-04-20 Β· 5 obs
β—‹ 2015-06-24 05:15:04
● 2015-11-02 06:10:10
● 2017-04-20 00:22:36
β—‹ 2026-04-06 14:50:54
β—‹ 2026-07-04 07:29:58
●NSns2.afternic.com2026-04-06 β†’ 2026-07-04 Β· 3 obs
β—‹ 2017-04-20 00:22:36
● 2026-04-06 14:50:54
● 2026-07-04 07:29:58
β—‹NSns2.undeveloped.com2015-11-02 β†’ 2017-04-20 Β· 5 obs
β—‹ 2015-06-24 05:15:04
● 2015-11-02 06:10:10
● 2017-04-20 00:22:36
β—‹ 2026-04-06 14:50:54
β—‹ 2026-07-04 07:29:58
β—‹NSsell.internettraffic.com2015-06-24 β†’ 2015-06-24 Β· 3 obs
● 2015-06-24 05:15:04
β—‹ 2015-11-02 06:10:10
β—‹ 2026-07-04 07:29:58
β—‹MXmx.problematically.com2016-01-20 β†’ 2017-04-20 Β· 4 obs
● 2016-01-20 14:58:40
● 2017-04-20 00:22:36
β—‹ 2026-04-06 14:50:54
β—‹ 2026-07-04 07:29:58
●A13.248.169.482026-04-06 β†’ 2026-07-04 Β· 3 obs
β—‹ 2017-04-20 00:22:36
● 2026-04-06 14:50:54
● 2026-07-04 07:29:58
β—‹A52.58.78.162016-04-14 β†’ 2017-04-20 Β· 5 obs
β—‹ 2016-01-20 14:58:40
● 2016-04-14 15:33:22
● 2017-04-20 00:22:36
β—‹ 2026-04-06 14:50:54
β—‹ 2026-07-04 07:29:58
β—‹A69.172.201.2082015-06-24 β†’ 2015-06-24 Β· 3 obs
● 2015-06-24 05:15:04
β—‹ 2015-11-02 06:10:10
β—‹ 2026-07-04 07:29:58
●A76.223.54.1462026-04-06 β†’ 2026-07-04 Β· 3 obs
β—‹ 2017-04-20 00:22:36
● 2026-04-06 14:50:54
● 2026-07-04 07:29:58
β—‹A80.240.129.102015-11-02 β†’ 2016-01-20 Β· 5 obs
β—‹ 2015-06-24 05:15:04
● 2015-11-02 06:10:10
● 2016-01-20 14:58:40
β—‹ 2016-04-14 15:33:22
β—‹ 2026-07-04 07:29:58

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
problematically.comns1.afternic.com, ns2.afternic.com-

βœ… Authoritative Response

Server:97.74.98.69

NS records: ns1.afternic.com, ns2.afternic.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for problematically.com (unsigned zone)

⏱️ Timing

Total: 118ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A276.223.54.146, 13.248.169.48
NS2ns1.afternic.com, ns2.afternic.com
MX1. (pri: 0)
TXT1v=spf1 -all
SOA1ns1.afternic.com dns.jomax.net

Analysis

Hierarchy

The domain mx.problematically.com falls under the parent problematically.com.

IP Addresses

problematically.com points to the IP addresses 13.248.169.48 and 76.223.54.146

corcer.com, adinet.co, ns1.gentworld.com and two other host names share IP numbers with problematically.com.

Name Servers

DNS delegation for problematically.com points to two name servers: ns1.afternic.com and ns2.afternic.com.

problematically.com uses the same name servers as several other domains β€” among them mail.hadak.com, etherealimage.com, host155.erosen.com and two more.

At least some of problematically.com's name servers are shared with other domains, for example socialink.us, glasford.org, vrgamers.com and two more.

These name servers tend to be deployed in combination with the name servers verification-m3erh32ujyoastvophjvuz.ns101.verify.hn and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn.

ns1.afternic.com directs to 97.74.98.69 and 2603:5:2126::45. ns2.afternic.com directs to 173.201.66.69 and 2603:5:2226::45. Each host name carries two IP addresses.