fetchr.com - dns.ninja

fetchr.com

com

Subdomains

Same first word

Similar names

DNS History

14 records (4 active, 10 former)

20162017201820192020202120222023202420252026NSns1.afternic.comns2.afternic.comns1.above.comns1.sedoparking.comns2.above.comns2.sedoparking.comMXlocalhostmail.nickstel.commx92.m1bp.commx92.mb5p.comA13.248.169.4876.223.54.146103.224.182.24472.52.4.120
β—‹NSns1.above.com2017-06-18 β†’ 2017-06-18 Β· 4 obs
β—‹ 2016-11-25 23:58:14
● 2017-06-18 06:55:04
β—‹ 2026-02-23 01:24:26
β—‹ 2026-07-14 06:46:16
●NSns1.afternic.com2026-02-23 β†’ 2026-07-14 Β· 3 obs
β—‹ 2017-06-18 06:55:04
● 2026-02-23 01:24:26
● 2026-07-14 06:46:16
β—‹NSns1.sedoparking.com2015-06-10 β†’ 2016-11-25 Β· 4 obs
● 2015-06-10 20:32:02
● 2016-11-25 23:58:14
β—‹ 2017-06-18 06:55:04
β—‹ 2026-07-14 06:46:16
β—‹NSns2.above.com2017-06-18 β†’ 2017-06-18 Β· 4 obs
β—‹ 2016-11-25 23:58:14
● 2017-06-18 06:55:04
β—‹ 2026-02-23 01:24:26
β—‹ 2026-07-14 06:46:16
●NSns2.afternic.com2026-02-23 β†’ 2026-07-14 Β· 3 obs
β—‹ 2017-06-18 06:55:04
● 2026-02-23 01:24:26
● 2026-07-14 06:46:16
β—‹NSns2.sedoparking.com2015-06-10 β†’ 2016-11-25 Β· 4 obs
● 2015-06-10 20:32:02
● 2016-11-25 23:58:14
β—‹ 2017-06-18 06:55:04
β—‹ 2026-07-14 06:46:16
β—‹MXlocalhost2016-11-25 β†’ 2016-11-25 Β· 4 obs
β—‹ 2016-04-16 02:01:22
● 2016-11-25 23:58:14
β—‹ 2017-06-18 06:55:04
β—‹ 2026-07-14 06:46:16
β—‹MXmail.nickstel.com2015-06-10 β†’ 2016-04-16 Β· 4 obs
● 2015-06-10 20:32:02
● 2016-04-16 02:01:22
β—‹ 2016-11-25 23:58:14
β—‹ 2026-07-14 06:46:16
β—‹MXmx92.m1bp.com2017-06-18 β†’ 2017-06-18 Β· 4 obs
β—‹ 2016-11-25 23:58:14
● 2017-06-18 06:55:04
β—‹ 2026-02-23 01:24:26
β—‹ 2026-07-14 06:46:16
β—‹MXmx92.mb5p.com2017-06-18 β†’ 2017-06-18 Β· 4 obs
β—‹ 2016-11-25 23:58:14
● 2017-06-18 06:55:04
β—‹ 2026-02-23 01:24:26
β—‹ 2026-07-14 06:46:16
β—‹A103.224.182.2442017-06-18 β†’ 2017-06-18 Β· 4 obs
β—‹ 2016-11-25 23:58:14
● 2017-06-18 06:55:04
β—‹ 2026-02-23 01:24:26
β—‹ 2026-07-14 06:46:16
●A13.248.169.482026-02-23 β†’ 2026-07-14 Β· 3 obs
β—‹ 2017-06-18 06:55:04
● 2026-02-23 01:24:26
● 2026-07-14 06:46:16
β—‹A72.52.4.1202015-06-10 β†’ 2016-11-25 Β· 4 obs
● 2015-06-10 20:32:02
● 2016-11-25 23:58:14
β—‹ 2017-06-18 06:55:04
β—‹ 2026-07-14 06:46:16
●A76.223.54.1462026-02-23 β†’ 2026-07-14 Β· 3 obs
β—‹ 2017-06-18 06:55:04
● 2026-02-23 01:24:26
● 2026-07-14 06:46:16

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
fetchr.comns1.afternic.com, ns2.afternic.com4 records

βœ… Authoritative Response

Server:173.201.66.69

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

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fetchr.com (unsigned zone)

⏱️ Timing

Total: 314ms | Queries: -

πŸ“„ Records

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

πŸ“Œ Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

Hierarchy

fetchr.com is a parent domain, with uxi.fetchr.com, www.fetchr.com and my.fetchr.com beneath it.

IP Addresses

fetchr.com resolves to the IP addresses 13.248.169.48 and 76.223.54.146

Additional host names β€” www.explicitscenes.com, zeus.jersey.net, drivenpower.com and two others β€” share IP numbers with fetchr.com.

Name Servers

The NS records for fetchr.com delegate to ns1.afternic.com and ns2.afternic.com.

fetchr.com shares its name server setup with other domains, including www.ranklite.com, ns2.carnesville.com, ichibanauto.com and two others.

fetchr.com has at least partial name server overlap with other domains, such as divorceshelp.com, l2w.net, pekgroup.com and two others.

These name servers are frequently paired with the name servers verification-d3jclucsp89ganyqbydeny.ns101.verify.hn, verification-k4ibaefv92b8mcahic8cdo.ns101.verify.hn, verification-kr7unxarkdyey3ajfo2lgy.ns101.verify.hn and two others.

ns1.afternic.com resolves to 97.74.98.69 and 2603:5:2126::45. Likewise, ns2.afternic.com resolves to 173.201.66.69 and 2603:5:2226::45 β€” two IP addresses apiece.